[FEATURE] auto-accept option for spawn_task tiles

Resolved 💬 1 comment Opened Apr 27, 2026 by leithl Closed May 30, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary

The mcp__ccd_session__spawn_task tool is the right primitive for parallel
work — opens a clean worktree + new chat without congesting the main
session's task bar. I use it constantly. The click-to-confirm chip becomes
a papercut at scale.

Problem

When directing several streams of work, the assistant proposes 3-4 spawned
sessions in a turn and each one waits for a click. The click isn't a
security gate (spawned sessions inherit the parent's permission mode either
way) — it's a "did you mean to fork?" check. When I've literally just typed
"spawn a task to do X", I clearly meant to.

Proposed Solution

Proposed solutions, in order of preference

  1. Per-call auto-accept the assistant can opt into when the user's

prompt is unambiguous (e.g. they said "spawn a task to..."). A parameter
on the tool call.

  1. settings.json flag (e.g. "spawnTask.autoAccept": true) for users

who trust the assistant's judgment globally.

  1. Keyboard shortcut to accept all pending chips as a middle ground.

Either 1 or 2 would let me use this primitive at the cadence the workflow
wants.

Environment

  • Claude Code (Cowork session UI, spawn_task chips)
  • macOS

Alternative Solutions

Clicking the button and bring a little sadder each time.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗