Troubleshooting

Install and runtime

• Confirm the downloaded binary matches your operating system and architecture.
• Confirm the install directory is on PATH, then open a new terminal after changing PATH.
• Run gjc --version and gjc --smoke-test to verify the standalone CLI.
• If native helpers fail, download the latest release again and inspect platform-specific output.

Session control

• If a session stops accepting prompts, verify owner liveness before submitting again.
• If branch metadata looks wrong, stop and correct the checkout instead of continuing in the wrong workspace.
• Retire stale sessions after preserving their terminal outcome.

SDK WebSocket and Coordinator MCP

• For direct SDK control, read the intended session's <repo>/.gjc/state/sdk/<sessionId>.json record and check its loopback url and credential; never copy that credential into logs or chat adapters.
• For multi-session automation, use Coordinator MCP's durable status and turn records instead of scraping terminal output or treating a per-session SDK connection as a coordinator.
• Invalid, stale, or denied authority should fail closed. Correct the intended session or configured Coordinator MCP mutation consent; do not widen authority blindly.
• Historical only: rpc, rpc-ui, and bridge were removed in v0.11.0 and have no compatibility path.

Website CI

1. Open the failed GitHub Actions run and start with the failed step in Validate website changes, whose job is Strict trusted validation.
2. For a pull request, check the reported base and head SHAs in the job summary; the workflow validates the candidate checkout with validator code from the trusted base, not candidate scripts.
3. Fix the reported HTML, link, metadata, or ownership issue in the pull-request branch and push a new commit. Do not work around a failure by changing CI permissions, bypassing checks, or modifying the trusted-validator boundary.
4. For whitespace failures, correct the patch whitespace reported by git diff --check. Release-sync branch failures can also be caused by generated-only ownership enforcement; keep manual edits outside generated release regions.