Slash commands
Type / in any Nebula message box to run a command — sharpen a prompt, plan before acting, clear context, or turn a request into a goal or a job.
Type / at the start of any message box and a list of commands opens. They do the things a sentence can't: stopping a turn, clearing context, or switching the agent into a mode. Everything else you can just ask for.
/plan migrate the billing service off the legacy queue
Reading the queue consumers and the billing service before proposing anything.
Ready to start on this plan — 4 steps, no writes until you approve.
How the palette works
Type / as the first character of an empty box. The list opens straight away and filters as you keep typing.
Pick one with the arrow keys and Enter, or click it. In the terminal, Tab completes the name without running it.
Add anything the command takes after a space — /enhance draft a launch email. The space closes the list, so the rest of the line is just your text.
Commands work anywhere you can type to Nebula: threads, channels, agent DMs, and the chat rail of a live call. They work in the terminal too.
Need a message to start with a literal slash — a file path, say? Type // and the rest goes through as ordinary text. A path in the middle of a sentence never triggers the palette anyway.
The commands you always have
These are on every account, in every workspace, with nothing to turn on.
| Command | What it does |
|---|---|
/enhance <prompt> | Rewrites a rough request into a sharper one, shows you the result, then runs it. |
/plan [request] | Turns on plan mode — Nebula works out an approach before changing anything. |
/clear | Clears the conversation's context. The thread stays; the agent starts fresh from here. |
/btw <question> | Asks a quick side question without disturbing the work in flight. |
/stop | Stops the turn that's running. |
/retry | Runs your last failed or stopped turn again. |
/help [question] | Gets you oriented, with a next step for whatever you're in the middle of. |
/goal <objective> | Sets up a goal — something pursued across many runs until it's done. |
/job <request> | Turns a request into a job on a schedule or an app event. |
Five of these need a conversation to act on. In a fresh box with no thread yet, /clear, /btw, /stop and /retry appear greyed out with Open a conversation first where their description would be.
/btw is genuinely a side channel. The question and its answer never enter the agent's history, so the work in progress doesn't get derailed by it — but consecutive /btw questions do remember each other, so you can follow one up.
Plan mode
/plan puts the thread into a read-only mode: Nebula investigates and proposes, but doesn't change anything until you say so. It stays on across follow-up messages rather than lapsing after one turn, so you can go back and forth on the approach first.
When it has one, the plan arrives as a card titled Ready to start on this plan, with the whole thing laid out to read.
Approves it. Nebula saves the plan as a PLAN.md file you can refer back to, leaves plan mode, and starts work.
Send written feedback instead of approving. Plan mode stays on and Nebula revises. There's no in-place editing — you say what should change and it rewrites.
Skips the approval card for you in this workspace from now on. Plans still get made; you just stop being asked to sign off.
Nebula skips the card when there's nobody there to answer it — work running from a job or a trigger goes ahead on its own rather than stalling on approval that will never come.
Your skills are commands too
Beyond the fixed list, the palette fills up from whatever the answering agent can actually reach. Every skill in your workspace shows up as /its-name, and connecting an app adds the commands that come with it — so the list on a research agent looks different from the list on one wired into your repo.
That's why this page doesn't try to enumerate them. Open the palette on the agent you're talking to and the list you see is the true one.
See a /command in a message and not know what it does? Click it. Nebula explains it in place rather than running it.
Related
Threads
Threads are individual conversations inside a channel, each with its own context and an auto-generated summary. Start, find, and use threads in Nebula.
Live
Start a live voice session with Nebula and your teammates from Home, a thread, or a channel — talk it through while agents work in the background.