Skip to content

fix(ci): target enableAllProjectMcpServers via settings, add diagnostics #1366

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BigSimmo merged 2 commits into from
Jul 28, 2026
Merged

fix(ci): target enableAllProjectMcpServers via settings, add diagnostics #1366

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
45bcda6
fix(ci): target enableAllProjectMcpServers via settings, add diagnostics
claude Jul 28, 2026
efe69b5
Merge branch 'main' into fix/claude-action-settings-diagnostic
BigSimmo Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions .github/workflows/claude.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,11 +69,16 @@ jobs:
# The action's default trigger phrase is "@claude"; it reads the
# triggering comment/review and acts on the current PR head.
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
# The action defaults to enableAllProjectMcpServers: true, which
# auto-loads this repo's .mcp.json (the "railway" server, launched
# via `npx @railway/cli mcp`). That server has no Railway session in
# a fresh Actions runner, and Claude Code fails fast (~2s, zero
# turns, no reply) trying to start it. --strict-mcp-config skips
# loading project/user MCP config entirely, so @claude runs here
# only with the action's own built-in tools.
# DIAGNOSTIC (temporary): claude_args: --strict-mcp-config (added in
# #1359) had no observable effect on the crash — the run still fails
# in ~2s with $0 cost and zero turns, meaning no model call is ever
# made. This action runs the Agent SDK's query() in-process rather
# than spawning the `claude` CLI, so claude_args may not map to
# --strict-mcp-config at all. Setting `settings` directly targets
# the JSON key the action logs writing itself
# ("Updated settings with enableAllProjectMcpServers: true").
# show_full_output is on to capture the real error since the prior
# two failures were both silent. Revert both once root-caused.
claude_args: --strict-mcp-config
settings: '{"enableAllProjectMcpServers": false}'
show_full_output: true