[FEATURE] You should know: "Investigate in background" option that forks a subtask instead of interrupting the main session

Open
#111,500 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

The note UI lives in the built-in cc-plugin-you-should-know plugin where the "Chat in main session" action is wired; read that first, then the existing /subtask and /fork commands to see how forks are created and how their results re-enter a session. Trace interactive-mode TUI action handling and the queue that defers output to turn boundaries. Done means a third action that forks with session context plus the note, returns a short finding, and queues it for the next idle point without touching shared state.

Written by the indexing model from the issue text.

Description

area:tui enhancement
Preflight Checklist
  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)
Problem Statement

I run Claude Code as a long-lived orchestrator: a board watcher, many parallel Codex runs, and VM work. The You should know mod (cc-plugin-you-should-know@builtin) often catches useful things, and I can open Learn more to discuss a note. But the only way to act on a note is "Chat in main session", which sends the topic into the main session.

That session is usually in the middle of orchestrating, so sending a note in:

  • interrupts the work it's doing,
  • gets lost in the queue behind it, or
  • spends main-session context and tokens on a side topic.

So I either dismiss good catches or handle them by hand (see Alternatives).

Proposed Solution

Next to "Chat in main session", add a third option: Investigate in background. When I pick it:

  1. Fork with context. A background fork starts with the main session's context, the note, and the Learn more chat including my comments.
  2. It investigates on its own. It reads code, checks facts, and drafts a fix or a recommendation, without touching the main session.
  3. It returns a short result. It hands back the finding, a proposed action, and a diff or plan if there is one. The result is queued for the main session's next idle point or turn boundary, never in the middle of a tool call.
  4. One step to resolve. I (or the main agent) can accept, act on, or dismiss the result in one step.

Nice to have:

  • A short queue indicator, like "2 background findings waiting".
  • Each result says which note it came from.
  • The fork follows the session's permission mode and never changes shared state (files, git, VMs, external services) without approval. By default it only investigates and proposes.
Alternative Solutions
  • Today: run /subtask or /fork by hand, paste the note in, wait, then copy the result back to the main session myself.
  • Send the note to the main session anyway, which costs focus and context.
  • Dismiss the note, which loses the catch.
  • #101325 asks for notes to go to the main thread automatically. That helps when the main session is free, but for an orchestrator it adds traffic. This request goes the other way, and both could exist as separate options.
Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

A real case from my session (a Heads up note I sent in with "Chat in main session"):

  1. The main session was orchestrating several parallel jobs: installing a throwaway Windows test VM and stepping it past setup screens, while two Codex runs built and patched a remote-shell tool.
  2. A Heads up note arrived mid-turn: the tool's approved plan said "outbound 443 only", but its tunnel actually needs an unusual outbound port that strict firewalls block.
  3. I sent it in. The main session stopped the VM work, researched a fallback design, and drafted a decision card inline. That cost main-session context and delayed the VM step.
  4. With "Investigate in background", a fork would have checked the claim, sketched the fallback options, and drafted the card, then queued a three-line summary for the next idle point.
  5. The main session would have finished the VM step without interruption, then shown me a ready-made decision with a single action.

Result: the catch is still handled, but the orchestrator keeps its focus and its context.

Additional Context

No response

Dominant language
TypeScript
Stars
156k
Forks
25k
Avg merge
16h 19m
Merged PRs (30d)
5

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.