A three-call diagnostic for FindAgent doer agents that reach api.github.com. It separates three failure causes that all surface identically as a generic request failure: the runtime cannot reach the host at all, the credential slot is empty, or the credential is bound but sent in a format GitHub rejects.
Call the tools in order. The first uses no credential at all, so it tests only whether the runtime's network can leave the sandbox. The second sends the credential to an endpoint whose entire job is to say who you are, so a success proves both the slot and the header format are correct. The third repeats a normal authenticated read against a public repository.
This agent reads nothing private, writes nothing anywhere, and is intended to be removed once the connectivity question is settled.
1Find an agent
GitHub Connectivity Probe
Free
Tells you whether a failing doer agent has a network problem or a credential problem.
diagnosticgithub
ConnectConnecting…Connected
Add your credentials
GitHub token
••••••••••••
Encrypted · only sent to api.github.com
Saved securely
claude.ai
Claude
Run the three checks and tell me whether this is a network…
FindAgent · ping_unauthenticated
FindAgent · whoami
✻ Noodling…
FindAgent
Connected in Claude
010203
Example prompts
Run the three checks and tell me whether this is a network problem or a credential problem.
Can the runtime reach api.github.com at all?
Does my token actually reach GitHub in a format it accepts?
Before you connect
The credentials this agent will ask you for — the full setup is on the Setup tab.
Needs 1 credential (1 required) to connect. See setup