Open and resume chats
In VS Code, run Embedder: New Embedder Chat in Editor or/new to open a chat in an editor tab. Each chat has its own model, mode, approvals, and queued messages.
Run /history to find a previous conversation in the selected project. You can search, rename, and reopen conversations. Closing an editor tab does not delete its conversation. Close a conversation before deleting it from history.
The terminal UI shows one conversation at a time. When resuming, choose Full Conversation or an earlier turn boundary. Resuming an earlier turn changes the conversation context; it does not restore project files.
Each conversation remembers its last mode. Resuming restores it; if that mode is unavailable, Embedder falls back to Act.
Send prompts during a turn
Sending a message while Embedder is working steers the active turn at its next step boundary. Use this to add a constraint, correct course, or supply missing information. Until the turn picks it up, the message waits in the queue. Explicitly queued messages wait for the turn to finish. Up to 10 messages can wait; any remaining messages run in order as new turns. Pending messages survive a client reload or restart. Use the queue controls to edit, remove, or move a message to the front. Send now moves it forward; it does not interrupt the current turn.In VS Code, stopping the current turn leaves queued messages in place. Remove follow-ups you no longer want. In the terminal,
Escape or Ctrl+C removes the latest queued prompt first; it stops the turn when the queue is empty. Each queued message keeps the mode selected when you sent it./btw <question> for a side question while the main task continues.
Undo or rewind
Use/undo to undo the last message, or /rewind to choose an earlier checkpoint. Read the choices carefully: you can revisit the conversation, restore file changes, or do both.
Before restoring files, review any work you have done since the checkpoint. A conversation change alone is not a file rollback.
Undo a rewind
A rewind remains undoable until you send the next message. Choose Undo rewind above the VS Code composer, or pressAlt+Z in the terminal, to restore the removed messages and the files the rewind reverted. You cannot undo a rewind while a turn is running.
Sending the next message commits the rewind, removes the truncated transcript, and drops queued prompts past the rewind point. A committed rewind cannot be undone.
Fork a response
In VS Code, use a fork to try another approach in a separate conversation:- Wait for the response to finish, then choose Fork to new chat beneath the response you want to branch from.
- In the new chat, hover over or focus Add chat transcript to preview the source conversation.
- Choose Add chat transcript if the new conversation should use those earlier findings and instructions, then send your next request.
Keep a long conversation useful
Run/compress when the conversation becomes long. Embedder condenses earlier context so you can continue the task; the transcript remains visible.
Smart auto-compact is an optional setting for supported models. It is off by default. Keep durable project instructions in EMBEDDER.md and confirmed facts in Project memory.
Share with your team
If sharing is available for your team, run/share and review the preview before confirming. Teammates receive a read-only snapshot.
/share list to review your shares and /share revoke to revoke shares for the active conversation.