[claude-code-user-docs-review] Claude Code User Documentation Review - 2026-08-22 #54792
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Claude Code User Documentation Review. A newer discussion is available at Discussion #55075. |
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
The docs list Claude Code as a first-class engine, and the example corpus backs that up: 39 workflow files use
engine: claudevs. 39 forengine: copilot— real parity. The problem isn't coverage, it's framing and setup gaps: Copilot is repeatedly called the "default" and the "start here" path,gh aw initsilently skips Copilot-only automation (custom agent, MCP auto-wiring) for Claude with no replacement documented, and there's a real trap where a Claude Code CLI user's existingCLAUDE_CODE_OAUTH_TOKENis silently ignored with a misleading error.Severity Findings
Critical Blockers
CLAUDE_CODE_OAUTH_TOKEN(what aclaude loginuser already has) "are not supported and are ignored if set... the workflow fails with an authentication error from the Claude CLI rather than any message mentioningCLAUDE_CODE_OAUTH_TOKEN." A Claude Code user following muscle memory will hit an opaque failure. —docs/src/content/docs/setup/quick-start.mdx:213Major Obstacles
initwith no Claude equivalent.gh aw init --engine copilotcreates.github/agents/agentic-workflows.mdand wires up MCP servers automatically; "Non-Copilot engines skip Copilot-specific artifacts" with no alternative flow documented for Claude users who want the same agent/MCP ergonomics. —docs/src/content/docs/setup/cli.md:159-164docs/src/content/docs/introduction/how-they-work.mdx:26,docs/src/content/docs/setup/quick-start.mdx:71ANTHROPIC_API_KEYbut gives no inline setup steps, unlike the API-key path. —docs/src/content/docs/setup/quick-start.mdx:122engine:from frontmatter falls back to Copilot, but nothing explains how to move an existing Copilot workflow to Claude or vice versa. —docs/src/content/docs/setup/quick-start.mdx:116,docs/src/content/docs/setup/cli.md:188Minor Confusion
docs/src/content/docs/reference/tools.md:65,68docs/src/content/docs/reference/tools.md:169docs/src/content/docs/introduction/architecture.mdx:192,288Engine & Tool Matrix
init)COPILOT_GITHUB_TOKENorcopilot-requests: writepermANTHROPIC_API_KEY(clear) or Anthropic WIF (link-only); OAuth token trapCODEX_API_KEYorOPENAI_API_KEYTool support is mostly engine-neutral (10 of 12 classified tools work across all engines per
docs/src/content/docs/reference/tools.md), but timeout defaults and web-search enablement are engine-specific and only sparsely explained. Parity observation from the example scan: Claude and Copilot are statistically even in the workflow corpus — the gap is entirely in prose/setup-flow, not example coverage.Auth Gaps
ANTHROPIC_API_KEYis documented clearly with a dedicated quick-start tab (docs/src/content/docs/setup/quick-start.mdx:207), the strongest part of the Claude onboarding path.quick-start.mdx:122).CLAUDE_CODE_OAUTH_TOKENrejection is documented but buried in a caveat rather than surfaced as a top-line warning before the auth section, and the resulting CLI error doesn't name the ignored variable, making it hard to self-diagnose (quick-start.mdx:213).ANTHROPIC_API_KEY) isn't spelled out next to the warning.Recommended Actions
Priority 1
claude loginlocally, that token will NOT work here — setANTHROPIC_API_KEYinstead," to pre-empt the silent-failure trap (quick-start.mdx:207-213).Priority 2
gh aw init, or explicitly state "no equivalent exists yet" so users stop searching (cli.md:159-164).quick-start.mdx:122).Priority 3
how-they-work.mdx:26andquick-start.mdx:71to avoid implying Copilot is more supported than Claude, given the example corpus shows parity.quick-start.mdx:116covering what changes (auth secrets, init artifacts) when moving a workflow between engines.All reactions