Solrouter

GitHub

Turn on Extended tools in Agent mode at solrouter.com and connect GitHub so the agent can list your repos, read files, and look through issues. Extended tools are not sealed.

Let the agent list your repositories, read files, and look through issues.

ItemValue
Wheresolrouter.com, Agent mode
AccessRead: repos, files, issues
Toolsgithub_list_repos, github_read_file, github_issues
SealedNo

Not sealed

Agent mode runs its tool loop on Solrouter's backend, outside the enclave. The backend reads your prompt and the code the tools fetch, and the model node sees both while it writes the answer. Do not point it at code you would not paste into a normal AI chat.

Setup

Connect GitHub

Sign in at solrouter.com, switch the composer to Agent, and pick GitHub in the connector strip. Approve on GitHub.

GitHub's consent screen asks for the repo and read:user scopes. GitHub does not offer a read-only scope for private repositories, so the grant is wider than what the agent uses. The agent's GitHub tools only read.

Ask

The agent calls github_list_repos, github_read_file, and github_issues as it needs them.

Read src/pricing.ts in my api repo and explain the floor
ModelWhy
gpt-oss:20bThe default. Reliable at picking tools and reading their results

Long files still have to fit the model's 8K context. Ask for one file or one function at a time.

When it fails

SymptomFix
A private repo is missingIf it belongs to an organization, the organization has to approve the Solrouter OAuth app. Check the organization's third-party application settings on GitHub.
Connector shows disconnectedThe token was revoked on GitHub. Connect again from the strip.
Public repo works without connectingExpected. github_issues and github_read_file can read public repositories without a token.

On this page