[claude-code-user-docs-review] Claude Code User Documentation Review - 2026-09-17 #61598
Closed
Replies: 2 comments
|
🤖 Smoke test bot says hi! This is an automated discussion interaction check from the Copilot engine smoke test suite. All systems humming along nicely. 🚀 Warning Firewall blocked 7 domainsThe following domains were blocked by the firewall during workflow execution:
To allow these domains, add them to the network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "update.googleapis.com"
- "www.google.com"
- "www.gstatic.com"See Network Configuration for more information.
|
0 replies
|
This discussion was automatically closed because it expired on 2026-09-18T12:55:21.757Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Executive Summary
A Claude Code user (no Copilot, no Copilot CLI) can complete gh-aw onboarding —
gh aw init --engine claudeskips Copilot-specific artifacts, andANTHROPIC_API_KEYsetup is documented step-by-step. But the docs consistently frame Copilot as the zero-friction default and leave Claude-specific gaps unresolved for the 10th straight day: theCLAUDE_CODE_OAUTH_TOKENfootgun (silently ignored, opaque failure) is still only a prose aside with no troubleshooting callout, and Claude has roughly half of Copilot's worked examples (56 vs 107 workflow files).Key finding:
docs/src/content/docs/setup/cli.md:240documents thatCLAUDE_CODE_OAUTH_TOKEN(e.g. fromclaude login) is silently ignored bygh aw secrets set— the run instead fails with a generic Claude CLI auth error that never names the token. This is the single most reported gap across the last 10 consecutive daily reviews.Severity Findings (Critical → Minor)
Critical Blockers: None this run (the OAuth-token gap was downgraded from Critical to Major on 2026-09-08 once it became documented in prose).
Major Obstacles
CLAUDE_CODE_OAUTH_TOKENgap — documented in prose but with no dedicated troubleshooting box; a user's natural instinct to reuse a localclaude logintoken still dead-ends in an unattributed error. (cli.md:240)gh aw initonly auto-scaffolds the custom agent file (.github/agents/agentic-workflows.md) and MCP wiring (.github/mcp.json,copilot-setup-steps.yml) for the Copilot engine. Claude/Codex users must hand-author an equivalent agent file "in your own agent's format" with no template shown. (cli.md:139-140).github/workflows/*.md— a Claude user scanning the repo for reference patterns finds a visibly thinner set. (repo-wide count)quick-start.mdxstill asymmetrically favors Copilot: "If you already have GitHub Copilot, start there — it requires no extra account setup" (line 72), while the Claude auth section defers WIF/OIDC setup entirely to an external page (lines 135-139) with no inline detail — unlike the Gemini tab, which gets one contextual WIF sentence (line 155).Minor Confusion
tools.timeout/startup-timeoutdefaults are only spelled out for Claude (60s) and Codex (120s); Copilot/Gemini/Pi defaults are unstated. (reference/tools.md:233-244)web-search:behavior is only concretely documented for Codex (disabled unless declared); other engines' behavior is left as "some engines require third-party MCP servers." (reference/tools.md:126-128)CODEX_API_KEYoverOPENAI_API_KEY); no equivalent alias/fallback is documented for Claude'sANTHROPIC_API_KEY, leaving it unclear whether alternates are tolerated. (quick-start.mdx:143-147vs.135-139).github/workflows/*.mduse several engine ids (opencode, aider, goose, crush, kiro, cursor, deepseek-harness, pydantic-ai) that aren't part of the "5 built-in engines" list docs advertise (Copilot, Claude, Codex, Gemini, Pi —architecture.mdx:17,how-they-work.mdx:26), which could confuse a reader about what's officially supported vs. experimental.Engine & Tool Matrix
copilot-requests: write) or fine-grained PAT (COPILOT_GITHUB_TOKEN); auto-scaffolds agent file + MCP wiringcopilot-requests: writeperm, or PATgh secret set ANTHROPIC_API_KEY; complete setup deferred to a separate pageANTHROPIC_API_KEYor Anthropic WIF (link-only);CLAUDE_CODE_OAUTH_TOKENsilently ignoredgh secret set OPENAI_API_KEY; documented precedence ruleCODEX_API_KEY(precedent) orOPENAI_API_KEYmodel:provider prefix, needscli-proxy: trueTool classification (from
reference/tools.md): of ~29 documented tools/features, 17 are cross-engine, 6 are Copilot-only (mostlygh aw initscaffolding +copilot-requests/COPILOT_GITHUB_TOKEN), 2 Codex-only, 1 each Claude-only and Gemini/Pi-only, and 2 ambiguous (web-search:, per-engine timeout defaults).Auth Gaps
quick-start.mdx:135-139andhow-they-work.mdx:33both link out to/gh-aw/reference/auth/#anthropic-workload-identity-federation-wif, a page outside this review's scope; Gemini gets a one-sentence inline nudge instead of a bare link (quick-start.mdx:155).CLAUDE_CODE_OAUTH_TOKENdead end — accepted-looking token is silently dropped; failure message never references it (cli.md:240). No troubleshooting section cross-links this from the quick-start Claude tab.gh aw init; Claude/Codex users get a pointer to "author it yourself," with no starter template linked (cli.md:139-140).CODEX_API_KEY>OPENAI_API_KEYorder, no alias/fallback behavior is described for Claude's key.Recommended Actions
Priority 1
CLAUDE_CODE_OAUTH_TOKEN, switch toANTHROPIC_API_KEY" callout directly in the quick-start Claude tab and nearcli.md:240, not just prose.Priority 2
.github/agents/agentic-workflows.md) sogh aw init --engine claudeusers aren't told to "author it yourself" with zero example.quick-start.mdx, matching the treatment Gemini already gets.Priority 3
web-search:behavior andtools.timeoutdefaults for Copilot/Gemini/Pi, not just Claude/Codex.Trend: This is the 26th consecutive daily run since 2026-08-22; the
CLAUDE_CODE_OAUTH_TOKENgap has now held at Major severity for 10 consecutive runs without a dedicated troubleshooting fix landing.References:
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
api.anthropic.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
All reactions