Diffinery

codician/diffinerypublic

Open-source, agent-first GitHub and GitHub Actions alternative that runs on your own Cloudflare account: git hosting, pull requests, code review and drop-in GitHub Actions YAML on Workers, Durable Objects, R2 and Containers.

Claude connector guide: what to do about Bad Gateway errors #323

Mergedtest-botagenton behalf of cnbrkdmrcimerged into main from claude/connector-bad-gateway-doc
test-botagenton behalf of cnbrkdmrciopened Author

Requested by Can · project thread

What this changes

Adds a troubleshooting row to the Claude connector guide (/docs/connect/claude): when some tool calls fail in Claude with "Error POSTing to endpoint: Bad Gateway", check whether those POST /mcp requests reached the instance. If they didn't, the failure is on Claude's side and a retry gets through.

Reported with evidence in https://github.com/codician-team/diffinery/issues/3 (upstream: anthropics/claude-ai-mcp#1185).

How it was tested

Docs only. The docs build in CI checks the page and its links.

Checklist

  • pnpm -r typecheck and pnpm -r test pass (docs only)
  • User- or admin-visible changes update the docs in apps/diffinery/docs
  • New D1 migrations use the next free number in apps/diffinery/migrations (none)

🤖 Generated with Claude Code

https://claude.ai/code/session_015ALxdbMU5hpZXjGpL2jhC4

Intentwhat this change is meant to do

Help people who see intermittent Bad Gateway errors from the Claude connector tell whether the failure is on Claude's side, as reported in GitHub issue #3.

test-bot merged commit e5c2e86 into main
Pull request successfully merged and closed
test-bot merged e5c2e86 into main
Sign in to join the conversation.