Dev & Code

Use GitHub with your AI chief of staff

OSP.net connects GitHub to a stateful, autonomous AI agent that actually does the work for you. Your agent works with your repos, issues and pull requests — scoped to exactly the repositories your token allows. It's a native integration — bring your own key and your agent is live in minutes.

Deploy your agent →

What is GitHub?

GitHub is a dev & code tool. With OSP.net, your AI agent connects to it directly so it can act on your behalf instead of just answering questions about it.

What your OSP agent can do with GitHub

How to connect GitHub

  1. RECOMMENDED — create a fine-grained token. Open the New fine-grained token page (sign in if asked). Give it a name like "OSP agent" and set an expiration. github.com → Settings → Developer settings → Fine-grained tokens → Generate new token
  2. Under Repository access, choose Only select repositories and pick exactly the repos you want the agent to reach (or All repositories if you prefer). This is the real access boundary — the agent can never see a repo the token can't.
  3. Open Repository permissions and grant — at minimum, for reading code and answering questions:
  4. Want the agent to also manage issues/PRs? Add these too (otherwise leave them off for a read-only agent):
  5. Click Generate token, then COPY it immediately — GitHub shows it only once. Paste it in the box above and click Connect.
  6. Prefer a classic token? It works too: New classic token → tick the `repo` scope for private repos, or just `public_repo` for public-only. Generate, copy, paste here. github.com → Settings → Developer settings → Tokens (classic) → Generate new token

Security: The token's repo selection and permissions ARE the agent's reach — a fine-grained token scoped to a few repos with Contents: Read-only is plenty for code questions and the safest default. Grant write only if you want the agent to open/edit issues and PRs. Revoke or rotate it any time from the same GitHub token settings page; your agent picks up the new key on its next restart.

Who uses GitHub with OSP

These roles commonly connect GitHub to their OSP agent:

Related dev & code integrations

Frequently asked questions

Can OSP.net connect to GitHub?
Yes. GitHub is a native OSP.net integration — you bring your own GitHub key or token, paste it in your dashboard, and your agent restarts live.
What can my OSP agent do with GitHub?
Your agent works with your repos, issues and pull requests — scoped to exactly the repositories your token allows. Specifically: Browse repositories, files and commits; Read, create and comment on issues and pull requests; Search code across the repos your token can see.
Is GitHub a native integration or via the gateway?
GitHub is a native, baked-in integration. You connect it with your own credentials, which are stored in an encrypted vault and injected only at runtime.
Is my GitHub data secure with OSP.net?
Yes. Your GitHub credentials live in an encrypted secrets vault, are injected only at container runtime, and are never written to disk in plaintext or used to train any model. Each customer runs in a fully isolated instance.

Get your GitHub AI agent →

← All integrations

Latest: v0.4.16