[Feature]: Ability to background inline subagents so the user can keep working in the thread

[artieeg]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/server

Problem or use case

When an agent is launched inline (synchronously, i.e. run_in_background: false), the parent turn blocks on that tool call until the child finishes. There is no way to move it to the background after the fact. If the child turns out to be long-running, the only options are to wait or to interrupt, which throws away the work.

The Claude SDK already models this: task_updated carries an is_backgrounded patch. T3 ingests the flag but does nothing with it, and never sends the corresponding control request:

• apps/server/src/provider/Layers/ClaudeAdapter.ts:3267 maps patch.is_backgrounded onto the task.updated event
• packages/contracts/src/providerRuntime.ts:633 types isBackgrounded
• apps/server/src/orchestration/Layers/ProviderRuntimeIngestion.ts:663 persists it into the activity payload

Nothing in packages/client-runtime, apps/web, or apps/mobile reads isBackgrounded, so it is stored and dropped. On the outbound side the only task-lifecycle control we send is Query.stopTask (ClaudeAdapter.ts:253, used on interrupt at :4413) — there is no background request path and no UI affordance for it.

Proposed solution

Two halves:

1. Outbound control — add a background-task control request alongside stopTask in the Claude adapter, plumbed through the same runtime command path that interrupt uses.
2. Surface state — render isBackgrounded in the Agents panel (a "Backgrounded" state on the agent row) and expose a "Move to background" action on a running inline agent. Once backgrounded, the parent's tool call resolves with a moved-to-background result and the completion notification arrives later, exactly as it does for agents launched with run_in_background: true.

Why this matters

Inline agents are the default for anything whose result you need before continuing, but you often only discover a task is slow after it starts. Today a misjudged inline launch costs you the whole turn: you either sit blocked or interrupt and lose the child's progress. Backgrounding turns that into a recoverable decision and gets control back to the user without discarding work.

Smallest useful scope

Just the outbound control plus a minimal Agents-panel action on running agents — no state persistence changes needed, since isBackgrounded already round-trips through ingestion. Even without any new UI badge, being able to trigger the background request and have the parent turn resolve would solve the blocking problem.

Alternatives considered

• Interrupting and relaunching with run_in_background: true — loses all of the child's in-flight work.
• Always launching agents backgrounded — defeats the purpose when the result is genuinely needed inline, and makes the model wait on notifications it could have had synchronously.
• [Bug]: No way to background or kill a long-running process, blocking further prompts/chats #1297 covers the same shape of problem for long-running Bash processes rather than subagents; related, but a distinct code path.

Risks or tradeoffs

• Race between the background request and the child completing on its own — the control request may land after task_notification, so the handler needs to no-op cleanly on an already-finished task (stopTask has the same acknowledgement-only semantics today, see the comment at ClaudeAdapter.ts:4436).
• Backgrounded children need to survive the idle session reaper; see [Bug]: Idle session reaper kills in-flight background agent work (dynamic workflows / subagents) #4198, which is the same hazard for agents launched backgrounded.
• Non-Claude providers have no equivalent control, so the action must be capability-gated rather than shown unconditionally.

Examples or references

Related: #1297 (background/kill long-running processes), #4198 (reaper kills in-flight background work), #5218 / #5529 (Agents panel visibility and lifecycle).

Contribution

• I would be open to helping implement this.