chore: replace secrets.ANTHROPIC_API_KEY with secrets.CLAUDE_CODE_OAUTH_TOKEN

[javdl]

Summary

• Replace secrets.ANTHROPIC_API_KEY with secrets.CLAUDE_CODE_OAUTH_TOKEN in 1 GitHub workflow file
• Migrates Claude Code GitHub Actions to use OAuth token authentication

Test plan

• Verify workflows trigger correctly with the new secret

🤖 Generated with Claude Code

---

[devin-ai-integration]

Devin Review found 1 potential issue.

View 3 additional findings in Devin Review.

[devin-ai-integration]

🟡 Commented-out config pairs anthropic_api_key param with OAuth token secret

The commented-out line # anthropic_api_key: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }} is semantically incorrect. The anthropic_api_key parameter expects an Anthropic API key, but CLAUDE_CODE_OAUTH_TOKEN is an OAuth token (as correctly used in .github/workflows/claude.yml:37 and .github/workflows/claude-code-review.yml with the claude_code_oauth_token parameter). If a developer uncomments this line, authentication will fail because an OAuth token is being passed as an API key. The original secrets.ANTHROPIC_API_KEY was the correct secret for this parameter name.

Suggested change

	# anthropic_api_key: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
	# claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1347e9a12e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use OAuth input instead of anthropic_api_key

The commented auth example now maps secrets.CLAUDE_CODE_OAUTH_TOKEN into anthropic_api_key, which is inconsistent with the rest of this repo (.github/workflows/claude.yml and .github/workflows/claude-code-review.yml both pass this secret via claude_code_oauth_token). If someone enables this optional line in claude-dispatch.yml, they will likely provide an OAuth token through the wrong input and hit authentication failures when the dispatch workflow runs.

Useful? React with 👍 / 👎.