[FEATURE] Detect diverging threads and offer to fork them into seeded conversations
Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 15, 2026
Summary
Long sessions often split into separate threads of work. Today they all share one context, which wastes context budget, cross-contaminates the threads, and makes past work hard to find. I'm proposing that Claude detect thread divergence and offer to fork each thread into its own conversation, seeded with a compact summary of the relevant shared context.
Scope
- Claude Code: CLI, IDE extensions, Claude Code on web and desktop.
- The Claude app: claude.ai web, desktop, and mobile. Filing it here too, since the Claude app has no public issue tracker. (It really should. This repo is the only place I know of where feedback gets a reply.)
Motivating example
One session in the Claude app went from drafting a long-form essay to designing a music-critic subsystem, a Spotify feature request, and a CD-ripping pipeline. Every thread was valuable. Together they crowded the essay's context, and finding any one of them later now means scrolling through all the others.
Proposed behavior
- Detection, then a prompt. When a conversation develops separate threads (different goals and deliverables, not just a tangent), the user gets a prompt, not an automatic action: a one-tap "Fork this thread?" suggestion in the UI, which they can accept, edit, or dismiss. Dismissing it silences the suggestion for that thread. The work in progress is never interrupted.
- Seeded forks. Each fork starts with a short, editable summary of the context it needs: decisions, constraints, links. Not the full transcript.
- Back-links. The parent and the forks link to each other, so the conversation becomes a findable tree instead of one long scroll.
- Claude Code mapping. A fork works like a branch for context. The summary is the merge base, and it could optionally pair with a git worktree.
Non-goals
- Automatic forking without asking.
- Splitting short tangents that wrap up in a turn or two.
Acceptance criteria
- In a session with two or more sustained, distinct threads, Claude offers a fork at most once per thread.
- A fork's seed lets the new conversation continue without the user re-explaining anything.
- Both conversations stay reachable from each other.