Troubleshooting

Health checks

gittensory-mcp doctor
gittensory-mcp status
gittensory-mcp whoami

Or hit the public API endpoint directly to confirm reachability:

GET https://gittensory-api.aethereal.dev/health

Common issues

Login hangs on device flow

Confirm you can reach github.com/login/device in your browser. Re-run gittensory-mcp login and paste the new code.

“Stale fidelity” warning

Upstream Gittensor changed. See Upstream drift for what that means and how to interpret cached analysis until fidelity recovers.

MCP not appearing in my editor

Re-run the appropriate init-client command and restart the editor. See MCP client setup for per-editor config locations.

401 Unauthorized from the API

Your Gittensory session expired. Run gittensory-mcp login again. Static bearer tokens are not user-facing.

API status & offline mode

The site continuously monitors the Gittensory API and surfaces problems through a banner under the header and a single deduped toast with a Retry button.

You're offline

We detected your browser is offline (navigator.onLine === false). Live API actions in the API reference are paused. Reconnect and the site auto-rechecks/health within a few seconds.

API unreachable

/health couldn't be reached at all. This usually means a network problem between you and the API edge. Try the Recheck button in the banner, or run curl https://gittensory-api.aethereal.dev/health from your machine to confirm.

API timing out

/health didn't respond within the 4-second probe window. The API may be slow or restarting. Retry — most timeouts resolve within a minute.

API degraded

/health returned a non-2xx response. Some endpoints may still work; check the Roadmap for incident notes or wait for the recheck cycle to clear.