Use Cases

Concrete scenarios that follow from how NEXUS is built — not a features list, but what each idea in Problem & Solution looks like in a session.

A specialized agent that's still there next month

You set up an agent with a specific role, a fixed working directory, and a short list of context tags for one recurring kind of work — say, reviewing a particular part of a codebase. Because that configuration lives on the agent's own identity rather than in a shell, it's unchanged the next time you start it, weeks later: same persona, same working directory, same on-disk memory. You only re-explain something once, when you first set it up. See Agents.

Two providers, one workspace, side by side

Different CLI agents are strong at different things. NEXUS lets you set a default provider per agent, so you can run one agent backed by one provider next to a second agent backed by another, in adjacent panes of the same window, working against the same files — without switching windows or re-authenticating each time. See Window & Panes.

Reasoning over a workspace instead of guessing

After a session touches a dozen files across a change, the Neural Map already shows which files that session touched and which other sessions or agents share them — because those connections are derived from what actually happened, not written down by hand. Searching the map for a file or a bit page jumps straight to its node; double- clicking a session's node opens the real session. See Neural Map.

Autonomy you control, not autonomy you hope for

An agent set to Approval — the default — pauses before each write action, so nothing lands without a look first. Setting a trusted agent to Auto for routine work doesn't remove the one boundary that matters: a destructive action still always pauses for your approval, regardless of which autonomy mode is selected. You choose how much supervision routine work gets, without having to choose it separately for the irreversible part. See Agents.

Working through one terminal together

Sharing a terminal lets someone else watch a live session without either of you losing track of who's actually typing: only one participant drives at a time, control changes hands by an explicit offer and accept, and the terminal always shows who currently has it. Useful for walking a teammate through a running session, or handing a long-running task off mid-stream. See Window & Panes.

A note now, found again through the graph, not a folder

Capturing a short note as a bit page while heads-down doesn't require deciding where it belongs — it becomes a node connected to whatever it was captured from, searchable by its own title or content later, whether that's days or weeks after you wrote it. You find it again by what it's connected to, not by remembering a folder. See Neural Map and Settings for the "Capture Bit" action available directly from a node.

Where to go next

• Problem & Solution — the ideas behind these scenarios.
• Agents, Neural Map, and Window & Panes — the guides for each surface.