Use the composer
The composer is the main control surface for a conversation. It combines a Markdown-oriented editor with run controls, model/mode/permission selectors, context usage, to-dos, suggestions, clipboard images, and voice.
Send and stop
Section titled “Send and stop”Enter and Ctrl/Cmd+Enter submit unless a completion menu is open. A new idle conversation starts a run. During an active turn, a normal prompt becomes a steering message and appears as a queued row in the transcript.
A queued prompt can be discarded or Cancel & Edit-ed back into the composer. Inline command prompts cannot queue. Stop targets the exact active run; Nerve suppresses duplicate stops and reconciles late completion events.
Completions
Section titled “Completions”Type / to filter available inline commands. Type @ to search files and directories in the current project. At most 80 completion options are shown.
@ is project path completion—not a mention system for people, agents, or conversations.
Suggestions
Section titled “Suggestions”Contextual prompt chips appear above the editor. Selecting one inserts or sends reusable content, depending on the suggestion. Built-ins cover common Git follow-ups; user and project definitions can add more.
Context and to-dos
Section titled “Context and to-dos”The toolbar displays current context-window pressure and cumulative usage when the provider reports it. A context value can remain unknown until a response. The to-do indicator reflects structured agent work state; it is separate from supervised background processes.
Review gates
Section titled “Review gates”A pending approval, question, or plan review disables normal composition. Resolve the card in the transcript. This keeps the decision associated with the exact tool or plan that requested it.