gh CLI, and credentials inside a managed sandbox. Use it when the agent needs to inspect or change GitHub repositories.
The GitHub connector requires
managed-deepagents>=0.4.0.Managed Deep Agents is in private beta, available on LangSmith Cloud in the US region only. Join the waitlist to request access.
Add the connector
Createconnectors/github.py or connectors/github.ts:
on_reuse / onReuse controls whether it keeps, resets, or fetches the checkout. The default is fetch.
Configure options
Repository paths must be relative and unique. Set
write to true on a checkout that needs write credentials.
For private repositories, configure GitHub credentials through identity. The runtime injects the resolved token as GH_TOKEN and configures Git credentials without storing it in thread state.
Test and deploy
Test the project locally withmda dev, then deploy it with mda deploy. Open deployment traces in LangSmith to inspect model calls, tool calls, errors, and latency.
The connector runs only when the project declares a managed sandbox. After startup, ask the agent to inspect the configured path or run gh auth status.
Next steps
Connectors
Compare connector types.
GitHub channel
Receive GitHub App webhooks.
Identity
Scope callers and resolve credentials.
Configure a sandbox
Configure sandbox scope and lifecycle.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

