dsh-side-session

When you are deep in a long DSH session—generating code, debugging, iterating—you often want to step aside quickly: "Would this pattern work better?" or "What does this API actually return?" Asking in the main thread pollutes the context; opening a fresh session throws away everything the main conversation has built. dsh-side-session is built exactly for this: click "Side Session" in the conversation header and a floating panel appears on the right. It forks every completed turn from the main session as reference context, then reads the in-memory log to fill in the live, still-open turn (submitted user messages, assistant replies, tool calls), so the side agent knows both the history and what is happening right now.

The side session mounts the exact same agent preset as the main one—identical tools, skills, prompts, permissions, working directory, and model routing—so it can start working immediately with zero extra configuration. A dual-boundary prompt (system section plus a first user message) explicitly tells the agent that the forked history is reference-only and that only messages after the boundary are active instructions, and that it must not interfere with the main thread. The side session never appears in the session list, and closing it disposes the agent and deletes the persisted files, leaving no trace behind.

It is designed for developers running long, complex DSH sessions who need a quick, non-destructive escape hatch: open the panel, ask an exploratory question, compare approaches, look something up, then close it. The main conversation is never touched, and the side session vanishes completely once you are done.