# Working with coding agents > **Section:** [Guides](https://networkteam.github.io/sdd/guides.md) > **Related:** [Browsing the graph](https://networkteam.github.io/sdd/guides/browsing-the-graph.md) · [Connected repositories](https://networkteam.github.io/sdd/guides/connected-repositories.md) · [Teams and processes](https://networkteam.github.io/sdd/guides/teams-and-processes.md) > **Also:** [HTML version](https://networkteam.github.io/sdd/guides/working-with-coding-agents) · [Docs index](https://networkteam.github.io/sdd/llms.txt) --- When you work with SDD in Claude Code or Codex, two sessions run side by side. Most surprises come from mixing them up. - **The agent session** is your conversation with Claude Code or Codex. It holds what the agent remembers. - **The sdd session** is the dialogue the `sdd` server tracks: which moves are running, at which step, and what they have collected so far. `/sdd` opens one, and its session ID is the only thing the agent needs to continue it. The agent keeps the two in step by carrying the session ID and following what the server serves. The tips below are about the situations where they drift apart. ## Capture what matters An sdd session is scaffolding, not a record. Only entries in the graph last. Anything worth keeping, a decision, an open point, the state of unfinished work, belongs in an entry. A capture you want to finish later can be started and parked, so it shows up as an open thread instead of living in the agent's memory. ## One sdd session per conversation - **Don't let two conversations drive the same sdd session.** If you fork or branch an agent conversation, both copies carry the same session ID. Each would advance the same moves while believing it is at its own position. Keep the sdd session in one copy, and run `/sdd` in the other to open a new session. - **Parallel agents each get their own session.** Several agents can work on one graph at the same time, each in its own sdd session. The graph is append-only and lives in git, so their entries do not overwrite each other. - **Tell the agent when you switch branches.** The agent declares which branch the session works on, so reads and captures land on the right branch. If you switch branches or move into a worktree yourself, say so. ## Don't rewind past a step sdd has taken Claude Code and Codex let you jump back in the conversation and continue from an earlier message. The sdd session does not jump back with you: a move that advanced stays advanced, and an entry that was written stays written and committed. After a rewind past such a step, the agent's memory and the session no longer match. - Rewind only to a point after the last sdd step. A move started before that point keeps running in the session even if the conversation no longer remembers it. - If you rewound too far, ask the agent to resume the sdd session. It then receives the current position again and continues from there. - To undo an entry, record a new one that closes or replaces it. Entries are never edited or deleted. ## Compaction When a conversation grows long, the agent compacts it into a summary. The sdd session survives this, as long as the session ID survives: - After compaction the agent should resume the sdd session, which serves every running move at its current step together with its instructions. - If the agent carries on from memory instead, skipping steps or answering for you, remind it: "Resume the sdd session first." - If the summary lost the session ID, the agent cannot find the session by itself. Give it the ID, or start a new session with `/sdd`. In practice it often works better to avoid compaction in long work. Capture the current state, for example as progress notes on the implementation or a partial done, and continue in a fresh agent session. ## Resume a session in a fresh agent session A session you did not wrap up stays open. In a new agent session, give the agent the session ID and ask it to resume that session. It receives the open moves at their current steps and can continue an unfinished capture or implementation where the old conversation stopped. Ask your agent for the session ID before you close a conversation you may want to continue. How best to hand work between agent sessions this way is still being worked out. Capturing the state as entries first is the safer path. ## Wrap up sessions At a natural stop, the agent offers to wrap up and names every thread that is still open. Wrapping up ends the session for good: an open thread left behind cannot be resumed afterwards. Finish the threads worth finishing, drop the others with a reason, and keep the session open if something should continue. Leaving without wrapping up costs nothing; the session stays resumable by its ID. ## In the dialogue - **Read the playback.** Confirming writes exactly what the agent showed. Ask for changes until it says what you mean. - **Override the pre-flight check only on purpose.** A serious finding stops the write; overriding is your call alone and is recorded on the entry. - **Say it in your own words.** The agent turns it into an entry and asks when something is unclear. You don't need to know the [entry kinds](/sdd/reference/entry-kinds/) or the [working modes](/sdd/working-modes/) by name.