Tangent and Rewind

Lesson 3 · Kiro CLI v3 for v2 users. Time: 8 minutes. Tangible win: branch, explore, and merge a finding back to the main chat.

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.

Primary source Tangent — kiro.dev. Commands, merge, use cases. About 4 minutes.

Commands

CommandDoes
/tangentAt root: branch into an auto-named side conversation. Inside one: go back a level
/tangent <name>Create or switch to a named tangent
/tangent lsVisual tree picker of all conversations
/tangent rootJump 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

SituationReach 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 editsVersion control. v3 has no /checkpoint
v2 habit to drop

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

  1. In a real session, send any message, then /tangent ddb and ask a side question.
  2. Run /tangent ls to see the tree, then /tangent merge root to send a summary home.
  3. Back in the main chat, ask "what did we learn about ddb?" to confirm only the summary arrived.
  4. Try /rewind once and notice what the new session starts with.
Ask me when a tangent beats starting a fresh session, or how tangents interact with compaction. Anything unclear? Ask.