Guide contents

Conversations, plans and AI work

Send a request

Create a conversation; choose a model/effort from the actual account catalog and select Plan or Build. Plan is read-only discovery/results. Build can create detached candidate work and studies. Enter sends; Shift+Enter inserts a line. Stop a running task before changing mode. Workspace preparation is local setup, not model thinking.

Tabs and saved work

Each tab is a conversation. Closing retains saved history; drag or use move-tab commands to reorder. Ctrl+Tab cycles, Ctrl+Shift+F searches conversations, Ctrl+F searches the transcript. Fork continues separately without shared mutable candidate files. Compact summarizes context while retaining history. Rename changes the label, not circuit identity.

Attachments and queue

Attach before sending; inspect/remove unintended file chips. Attachments belong to the submitted request. While busy, Queue retains a distinct pending request, not a completed or already-running response. Preserve a newer unsent draft while queued work completes. Inspect queue details for held/cancelled items. Stop affects this conversation, not other tabs. Restart recovery uses persisted request identities, not a new empty conversation.

Questions, tools and helpers

Open an awaiting question, answer and submit. Preselected options are not answers until submitted. Tool/helper rows show actual lifecycle and public summaries, never private reasoning. Expand errors; a failed shell command alone does not establish overall success/failure. Elapsed time is recorded work, not a progress estimate.

Implement plan

Review the canonical plan and choose Implement plan. This submits the exact plan in Build with a fresh input snapshot and stable request identity; it is not a draft-only handoff. Other drafts/files survive. Implementation never accepts a candidate, grants approval or applies to Original.

Review, edit and Retry

Inspect differences and retained evidence before human Apply. Retry uses the exact failed request without automatic inference retries. Editing/resending is a deliberate new request. Rebase prepares review against the current source and can expose conflicts. See Accounts, Tools and Recovery.