Projects: let a decision-card choice count as the user's approval in auto mode threads

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

In Claude Code Projects I answer the coordinator's decision cards in the project conversation. When the decision is something auto mode treats as risky (a deploy, a cutover, moving a file outside the working folder), the coordinator passes my choice to the thread, and the thread on my laptop is refused, because auto mode only accepts my own message naming the action. A relayed card choice never counts.

So every such decision costs me two steps: I tap the card, then I copy a sentence the coordinator writes for me ("I approve the runtime cutover to commit ... for issue ...") and paste it into the chat so it can be attached to the thread. On a busy day that is a dozen round trips for decisions I already made with a tap.

What I tried, on 2 Oct 2026:

• Starting the laptop folder's Remote Control server with --permission-mode bypassPermissions. Its sessions start in bypass, but a project thread is switched back to auto mode as soon as the project picks it up (the thread transcript shows permissionMode: auto).
• An autoMode.allow entry describing the coordinator's relay of a card choice as my intent. My own session's safety check refused to proceed with it as an auto mode bypass, which is fair: I should not be able to get around the classifier with prose. The fix belongs in the product.

Proposed Solution

Make a decision-card choice count as the user's own explicit intent for the action the card names, end to end:

• When a thread needs approval, it can raise a card whose option names the exact action, and the user's tap is recorded as a user-authored approval for that action, visible to auto mode in that thread.
• Or: a per-project setting for the permission mode of laptop threads, so a user who accepts the risk can choose bypass for their own machine.

Alternative Solutions

Today: copy and paste a pre-written approval sentence for every gated step, or type it in the thread itself. It works, but it turns a one-tap decision into a context switch, and it is the main thing standing between me and leaving projects to run unattended.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

1. A daily pipeline thread needs a runtime cutover, which auto mode gates.
2. The coordinator asks me on a card: "Cut over to commit abc1234 for today's issue?" I tap Yes.
3. Today: the thread is refused, the coordinator writes an approval sentence, I copy and paste it, and the thread retries.
4. With this feature: my tap is the approval, and the thread proceeds.

Additional Context

Claude Code 2.1.287 on Linux, Max plan, Projects with laptop folders served by claude remote-control. Related: #98923 (free-text answers in decision cards), #98655 (notifications for cards).