# Rationale — "Why is my coding agent sitting on a permission prompt?"

FRE-199 item 1, page 2 of the first pair. Drafted 2026-11-05 by CMO.

## The phrase

Primary: **"claude code waiting for permission"** and the away-from-desk variant
("approvals when you're away from the computer"). First phrase on the standing
list (`drafts/listening.md` §The phrase list).

## Why this phrase won the slot

- **The strongest single thread in the backlog.** r/ClaudeAI 1xhbc71 (2026-10-28,
  47 comments and moving) asks the buying question outright: kicked off a long
  task, came back an hour later, agent had been sitting on a permission prompt
  for 55 minutes. The thread's own answers (remote control, tmux+SSH,
  skip-permissions, allowlists) prove demand; none of them makes the wait
  visible at the machine — that is the honest gap this page answers without
  naming anyone.
- **The week's objection vocabulary.** Scans 1–9 keep returning "the model keeps
  handing control back" and "stops and waits for me" — permission friction is
  the category's core complaint, not a niche one.
- **Recurring independent accounts.** The invisible-permission theme has three
  independent accounts in one week (1xksutq — gh used without a visible prompt;
  1xkejsp's Linux panel; the scheduled-tasks silent-stall finding), so the
  search demand is not one loud thread.
- **Wedge-aligned.** This is the literal wedge sentence's territory — "an agent
  blocked on a permission prompt is the most expensive kind of idle" — answered
  with the agent's own documented mechanism.

## Deliberate scoping

This page owns the **blocked-half** of the approval problem (why prompts happen,
how to make them rare, how to make the wait visible at the machine). The
**away-half** (controlling a remote agent from elsewhere) is a different phrase,
a different page, and one where the honest answer is dominated by the agent
vendor's own remote feature — the page deliberately does not go there
(`drafts/listening.md` Scan 1 category intel #1).

## Evidence trail

| Thread | Date | What it showed |
|---|---|---|
| r/ClaudeAI 1xhbc71 — "How do you handle Claude Code approvals when you're away from your computer?" | 2026-10-28 | 55-minute wait on a permission prompt; 47 comments of demand; "what's still annoying about your setup?" |
| r/ClaudeCode 1xkoz06 — "How permissive are you with AI and for how long?" | 2026-10-31 | The undo-split: "file edits, tests and branches get a free hand, since git is the undo. Anything that reaches another person … stays on confirm" |
| r/ClaudeCode 1xksutq — gh used without visible prompt | 2026-11-01 | Third independent invisible-permission account of the week |
| r/ClaudeCode 1xkejsp — Linux panel app | 2026-10-31 | Per-session "Needs You" differentiation shipping elsewhere; the need is real and cross-platform |

All rows live in `drafts/listening.md` with URLs and verbatim quotes.

## Gates before this page ships

1. **Sponsor fact-check** of the claims table in `copy.md` (owner: Michael
   Freno); page moves `pending/` → `approved/` on his read.
2. **CTO eyes on the agent-behaviour claims** — all eight doc-sourced claims
   re-read 2026-11-05; the FRE-199 plan routes anything asserted about an
   agent's behaviour to the CTO.
3. **Publish path:** `pending/` → `approved/` → a human places it on
   nook.freno.me (blog route). Nothing posts itself.

## Ban compliance (FRE-199 + positioning.md rule 1)

- The Nook: not named; notch/island/companion not mentioned.
- Competitors: not named — including the agent vendor's remote feature, which
  the page never needs to mention because it stays on the at-the-machine half.
- Claude Code is named only as the subject whose documented permission system
  the page explains, with its own docs as the source — same status the
  listening phrase list already gives it.
- No superlatives, no benchmark numbers, no invented testimonials, no price,
  no roadmap dates.

## Cadence note

Second page of the first pair. Queue behind it: multi-agent tracking ("How do
you keep track of multiple coding agents running in parallel?", 1xm6frp,
2026-11-03) and the invisible-permission cluster — the queue holds above the
three-candidate floor, so the two-a-week cadence holds.