Tangent and Rewind
v1's experimental tangent was a single checkpoint toggled with Ctrl+T. In v3, a tangent is a full, named, nestable session that inherits your context and stays isolated. /rewind is its sibling: it forks from an earlier turn. Both exist to protect your main thread's context.
Commands
| Command | Does |
|---|---|
/tangent | At root: branch into an auto-named side conversation. Inside one: go back a level |
/tangent <name> | Create or switch to a named tangent |
/tangent ls | Visual tree picker of all conversations |
/tangent root | Jump to the main conversation from any depth |
/tangent merge [dest] | Send a short summary of this tangent to the parent (default), root, or a named session |
A footer chip shows where you are. You need at least one message before you can branch. Nothing inside a tangent reaches the parent unless you merge, and merge never creates a session.
When to use which
| Situation | Reach for |
|---|---|
| Quick lookup, noisy debugging, "dumb question" | /tangent |
| Compare two designs from the same starting point | /tangent approach-a, /tangent approach-b |
| Redo from an earlier prompt, keep file changes so far | /rewind (forks a new session; files untouched) |
| Undo the agent's file edits | Version control. v3 has no /checkpoint |
The experimental /checkpoint that restored files is not available in v3. Commit (or stash) before letting the agent run long, and use rewind only for the conversation. Sessions have their own store; browse, bookmark and rename them in the /sessions pane.
Retrieval check
You spend fifteen turns debugging inside a tangent. What does the main conversation hold afterward?
Right. Tangents are isolated; only an explicit /tangent merge carries a summary back.
Isolation is the point: nothing crosses back until you run /tangent merge.
The agent edited the wrong files and you want them back. What fits best?
Right. Rewind never touches files, and v3 has no checkpoint restore; git is the file safety net.
Rewind forks only the conversation, and tangents do not touch files either. Use version control.
You are two tangents deep. Which command sends findings to the main conversation?
Right. merge root targets the main conversation regardless of depth.
A bare merge targets only the parent. merge root skips straight to the main conversation.
Practice
- In a real session, send any message, then
/tangent ddband ask a side question. - Run
/tangent lsto see the tree, then/tangent merge rootto send a summary home. - Back in the main chat, ask "what did we learn about ddb?" to confirm only the summary arrived.
- Try
/rewindonce and notice what the new session starts with.