Executive Summary

A developer who uses Claude Code and deliberately avoids GitHub Copilot can adopt gh-aw — Claude is a first-class engine (engine: claude), ANTHROPIC_API_KEY setup is documented in two places, every documented tools: entry is engine-agnostic, and gh aw init --engine claude skips all Copilot scaffolding. There are no Critical blockers. The friction is structural: GitHub Copilot is the documented default engine, and all 7 example workflows in docs/.../examples/ set no engine — so a Claude user who copies an example silently runs on Copilot and is asked for COPILOT_GITHUB_TOKEN they neither have nor want.

Persona Context

• GitHub ✅
• Claude Code ✅
• GitHub Copilot ❌
• Copilot CLI ❌

Severity Findings

Engine Comparison

(occurrence = repo-wide engine: frontmatter field count, includes docs/specs; treat as relative volume not a workflow census.)

Tool Availability

tool-engine-classifier found every documented tools: entry is engine-agnostic — 0 copilot-only, 0 claude-only, 0 codex-only.

Note: there is no copilot tool — Copilot-specific knobs (engine.agent, engine.harness, max-continuations) live under engine:, not tools:. So a Claude user loses no tooling.

Authentication Gaps

From auth-doc-extractor (reference/auth.mdx):

• Good for Claude users: the Anthropic key path is the simplest of all engines and is documented.
• Explicit warning worth surfacing: CLAUDE_CODE_OAUTH_TOKEN is not supported and silently ignored — only ANTHROPIC_API_KEY works (auth.mdx:121-123). A Claude Code user who expects to reuse their Claude subscription OAuth token will be confused; this is in auth.mdx but not in Quick Start.
• Gap: no canonical secret guidance for the "custom" path.

Example Parity

engine-example-counter: Claude has broad coverage of core safe-outputs (create-issue, create-pull-request, add-comment/labels, mcp, github-remote-mcp, noop) across all engines, but Copilot-only fixtures exist for ~25 newer features (projects, review-thread resolve/submit, dispatch-workflow, comment-memory). Claude sample workflows: .github/workflows/scout.md, deep-report.md, smoke-claude.md.

Recommended Actions

Priority 1 (close the silent-Copilot trap):

1. Add engine: claude (or an engine note) to the 7 docs/.../examples/** workflows, or a prominent "examples default to Copilot" banner.
2. Add a Quick Start callout: "Not a Copilot user? Choose Claude at the engine step and set ANTHROPIC_API_KEY."

Priority 2 (reduce opt-out friction):
3. Promote gh aw init --engine claude to a top-level example in setup/cli.md.
4. Surface the CLAUDE_CODE_OAUTH_TOKEN-unsupported warning in Quick Start, not only auth.mdx.

Priority 3 (parity & guidance):
5. Add an engine-capability comparison ("why Claude vs Copilot", max-turns vs max-continuations).
6. Add Claude examples for advanced safe-outputs to match Copilot fixture coverage.
7. Document that there is no custom engine; point to engine.command/engine.harness.

Conclusion

Can Claude Code users adopt gh-aw? — Yes. Claude is genuinely first-class: documented auth, engine-agnostic tools, and a clean Copilot-free init path. The problems are defaults and discoverability, not capability — the biggest risk is a Claude user copying an engine-less example and being unexpectedly funneled into Copilot.

Overall adoptability score: 7.5 / 10 — fully usable today, held back by Copilot-default framing and example workflows that don't declare an engine.

References:

• §27062726552

Generated by 📝 Claude Code User Documentation Review · 359.5 AIC · ⌖ 14.1 AIC · ◷

• expires on Jun 7, 2026, 12:58 PM UTC