Repository navigation
[claude-code-user-docs-review] 🔍 Claude Code User Documentation Review - 2026-09-10 #59973
Closed
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-09-11T12:53:24.620Z.
|
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 GitHub Copilot) can complete Quick Start using
ANTHROPIC_API_KEY, but the docs still steer new users toward Copilot as the assumed default, and theCLAUDE_CODE_OAUTH_TOKENpitfall — flagged for 19 consecutive daily runs since 2026-08-22 — remains buried in CLI prose instead of surfaced where a Claude Code user actually authenticates. Key finding: the bigger accessibility gap this run isn't auth clarity, it's example parity — Copilot ships ~2x as many workflow examples and 9 dedicated smoke tests for advanced config (Azure auth, ARM runners, model tiers, sub-agents) versus 3 for Claude with no equivalent coverage.Severity Findings
Critical / Major / Minor findings (click to expand)
Critical Blockers: none this run (unchanged from the last 2 runs — the OAuth-token issue remains downgraded to Major since it's now documented in prose).
Major Obstacles
CLAUDE_CODE_OAUTH_TOKEN(e.g. fromclaude login) is silently ignored, causing an opaque downstream Claude CLI auth failure that never names the token — documented only as plain prose atdocs/src/content/docs/setup/cli.md:240, absent from the Claude tab a new user actually follows atdocs/src/content/docs/setup/quick-start.mdx:134-138. Unresolved across 19 consecutive daily runs since 2026-08-22.docs/src/content/docs/introduction/how-they-work.mdx:33gives only a bare link, unlike Gemini's explicit inline recommendation ("To avoid a long-lived key, configure Google Workload Identity Federation") atdocs/src/content/docs/setup/quick-start.mdx:151..github/agents/agentic-workflows.md,.github/mcp.json,copilot-setup-steps.yml) is generated automatically only on the Copilotgh aw initpath (docs/src/content/docs/setup/cli.md:115,139); Claude users are told to hand-author an agent file in "your own agent's format" with no worked example.Minor Confusion
docs/src/content/docs/introduction/architecture.mdx:17lists 4 engines (omits Pi) whiledocs/src/content/docs/introduction/how-they-work.mdx:26lists 5.architecture.mdx:304labels the engine box "(Copilot, Claude, Codex)" only, leaving Gemini/Pi coverage undocumented there.docs/src/content/docs/reference/tools.md:144gives Codex a dedicated tool-restriction callout (web-search disabled by default) but no equivalent Claude-specific tool-availability note beyond a one-line timeout default (tools.md:255).anthropic/prefix,openai/codex/prefix) is described only at a high level athow-they-work.mdx:36, with no worked example — relevant to Claude users routing through Pi.Engine & Tool Matrix
quick-start.mdx:73)reference/engines.md:22)copilot-requestswrite orCOPILOT_GITHUB_TOKEN(how-they-work.mdx:32)ANTHROPIC_API_KEY(quick-start.mdx:135) or WIF (link only)ANTHROPIC_API_KEY; OAuth-token silently ignored (cli.md:240)OPENAI_API_KEY/CODEX_API_KEY(quick-start.mdx:140-144), precedence documented clearlycli.md:139)smoke-*)Tool classification (from
reference/tools.md): 11 tools are universal/engine-agnostic (edit, github, bash, web-fetch, playwright, cache-memory, etc.); 1 Codex-specific restriction (web-search off by default,tools.md:144); 1 Claude-specific note (60s vs Codex 120s timeout default,tools.md:255); 1 Pi-specific requirement (tools.cli-proxy: true+gh-proxymode,quick-start.mdx:156).Parity note from the example scan: for a Claude-only user, roughly 43% of tagged example workflows aren't directly usable as Claude references, and the smoke-test suite demonstrates Copilot's advanced auth/runner/model-tier surface far more thoroughly than any Claude equivalent.
Auth Gaps
copilot-requests/COPILOT_GITHUB_TOKEN; Claude →ANTHROPIC_API_KEYor unlinked WIF; Codex →CODEX_API_KEY(precedence) orOPENAI_API_KEY; Gemini →GEMINI_API_KEY+ linked WIF; Pi → inherits from model-prefix engine.gh secret set ANTHROPIC_API_KEY,quick-start.mdx:135-137) but has no WIF walkthrough, unlike Gemini's.cli.mdalready uses[!NOTE]-style callouts for lower-severity issues (e.g. line 416 Codespaces permission note, line 468 HTTP 404 log warning) but the OAuth-token trap at line 240 — arguably more disruptive since it produces a misleading error — is still plain prose, not a callout.Recommended Actions
Priority 1
CLAUDE_CODE_OAUTH_TOKENwarning fromcli.md:240prose into a[!WARNING]callout, and duplicate/link it directly inquick-start.mdx's Claude tab (near line 134-138) where users actually authenticate.quick-start.mdx:151) instead of a bare link.Priority 2
cli.md:139) with a worked Claude Code subagent example.Priority 3
architecture.mdx:17andhow-they-work.mdx:26(Pi omission) and update the MCP sandboxing diagram (architecture.mdx:304) to note Gemini/Pi coverage explicitly.Trend: This is the 19th consecutive daily run flagging the OAuth-token documentation gap (first seen 2026-08-22, downgraded from Critical to Major on 2026-09-08 once prose coverage landed). It remains unresolved at the quick-start entry point.
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