Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneesstack72

Relationships

#3764 Local verification docs still tell agents to put ANTHROPIC_API_KEY in verify.env for reviews

Opened by skunk-ape · 10/22/2026· Shipped 10/22/2026

The local verify-reviews workflow is meant to run its Claude reviews through claude -p on the developer's claude.ai login. scripts/setup_verify_env.ts already leaves ANTHROPIC_API_KEY out of verify.env for that reason, and verification-conventions.md lines 152-153 say the trigger evals and the reviews both run on the claude.ai login.

Two docs still present the API key as the first option for local runs:

  • agent-constraints/verification-conventions.md lines 113-118 (Authentication): lists verify.env with ANTHROPIC_API_KEY as method 1 and the claude.ai login as the fallback.
  • .claude/skills/issue-lifecycle/references/verification.md line 48: says reviews need verify.env with ANTHROPIC_API_KEY, or a claude.ai login.

Agents follow these, keep a key in verify.env, and source it before launching verify-reviews. claude -p then prefers the key over the login; when the key goes stale every review fails within a second with Invalid API key, and no review runs.

Fix: rewrite both passages so local reviews use the claude.ai login only, and say ANTHROPIC_API_KEY is for CI (the API route). Docs only: the review workflow keeps passing the key through, since CI may use it.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 9 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

10/22/2026, 4:04:28 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack7210/22/2026, 3:10:02 PM

Sign in to post a ripple.