[claude-code-user-docs-review] 🔍 Claude Code User Documentation Review - 2026-10-01 #64769
Closed
Replies: 1 comment
|
This discussion has been marked as outdated by Claude Code User Documentation Review. A newer discussion is available at Discussion #65018. |
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 onboard today —
ANTHROPIC_API_KEYis documented atdocs/src/content/docs/setup/quick-start.md:147-151, and theCLAUDE_CODE_OAUTH_TOKENsilent-ignore gap that blocked 29 consecutive daily runs since 2026-08-22 is still documented (quick-start.md:153,cli.md:240). The remaining friction is structural, not a hard stop:gh aw initstill only auto-scaffolds a custom-agent file/MCP wiring for Copilot, Claude has ~1.9x fewer example workflows than Copilot, and Claude's WIF setup is link-only versus inline detail for other engines.Severity Findings
Critical Blockers (0)
None. Core auth path for Claude (
ANTHROPIC_API_KEY) is documented and functional end-to-end.Major Obstacles
gh aw initartifact parity gap — only the Copilot engine path auto-creates the Agentic Workflows custom agent file (cli.md:115); Claude/Codex users get no equivalent scaffolding or pointer to do it manually (cli.md:139-140)..github/workflows/*.md; newer engines (aider, goose, opencode, kiro, cursor, crush, etc.) each have a dedicatedsmoke-<engine>.md, but Claude's own smoke coverage is comparatively thin, making it harder to find a worked Claude example to copy.quick-start.md:155links out to a separate "Using Claude Code with GitHub Agentic Workflows" guide for complete setup and defers WIF entirely to a reference-doc link (quick-start.md:151), whereas Codex's setup (quick-start.md:159-163) is fully inline with no second hop.Minor Confusion
tools.md:128disablesweb-searchby default for Codex/Claude/Copilot but never states whether Gemini/Pi differ — a Claude user can't tell if the restriction is engine-specific or universal.quick-start.md:72-77) lists "AI Account" as a generic step without noting Copilot uniquely needs no separate account creation — reads as if every engine needs an external signup.tools.md:43,63) don't state whether the read-only/cli-proxy caveats apply uniformly across engines or only some.Engine & Tool Matrix
COPILOT_GITHUB_TOKENPAT, inline (quick-start.md:135-143)ANTHROPIC_API_KEYinline, WIF link-only, extra guide hop (quick-start.md:147-155)OPENAI_API_KEY/CODEX_API_KEY, fully inline, no second hop (quick-start.md:159-163)gh aw initscaffoldingcli.md:115)cli.md:139-140)counts_by_enginethis run — effectively 0 standalone examplesCODEX_API_KEY>OPENAI_API_KEY)Universal tools (edit, github, bash, web-fetch, playwright, cache-memory, repo-memory, agentic-workflows, cli-proxy — 9 of 14 classified) work identically across all engines per
tools.md, so the gap is onboarding/scaffolding, not runtime capability.Auth Gaps
CLAUDE_CODE_OAUTH_TOKENis explicitly called out as unsupported/silently-ignored in bothquick-start.md:153andcli.md:240.quick-start.md:151), with no inline example the way the Gemini/Codex sections provide; a Claude user evaluating "key vs. WIF" has to leave quick-start to decide.Recommended Actions
Priority 1 — Add a
gh aw init --engine claude|codexscaffolding path (or explicit manual-steps callout) atcli.md:139-140so non-Copilot users aren't silently left without the custom-agent/MCP wiring Copilot users get for free.Priority 2 — Inline a minimal Anthropic WIF example directly in
quick-start.md(near line 151) instead of a bare link, mirroring the Codex section's self-contained style.Priority 3 — Backfill Claude-specific smoke/example workflows toward parity with Copilot (currently ~52%), and add one line to
tools.md:128clarifying whetherweb-searchdefaults differ for Gemini/Pi.Note on this run:
.claude/agents/doc-reader.mdand.claude/agents/engine-example-counter.mdagain lacked the requiredname:frontmatter field and failed to register as custom agent types (17th consecutive day this has recurred). AnEditattempt to addname: doc-reader/name: engine-example-counterwas denied by permissions again. Findings above were gathered via two parallelgeneral-purposefallback agents carrying the original instructions inline — filed separately viamissing_tool.References:
All reactions