CONNECTOR · GITHUB
Ground every plan in your GitHub code.
A connector is the bridge to your code. This one gives the planning agent read-only access to a GitHub repository, so every Spec fits the product as it works today instead of the one anyone remembers. You never open the repo. The agent does, and it never changes a line.
What the agent reads
Link a repository and the agent reads your GitHub code while it interviews you, so every Spec fits the product as it works today. Read access only. It never changes a line.
| What Plansmith reads | What it grounds |
|---|---|
| Repository files and folders | Where things live, so a Spec names the real modules instead of a guess |
| File contents on the default branch | How the product works today, so the plan starts from what exists |
| Code search across the repository | The exact places a change lands, before anyone sizes it |
| Framework, styling, and component conventions | A prototype that looks like your product, not a generic mockup |
| The repository you link to a Project | Code context on every Plan in that Project |
| Nothing else | Read access only. The agent never writes, commits, branches, or opens a pull request. |
Three steps to grounded plans
- 1
Connect
Click Connect GitHub and approve Plansmith for the organization whose code you want to plan against. Connections are personal and access is read only. If your organization requires an admin to approve new apps, send them this page.
- 2
Link a repository
Pick the repository this Project plans against. The agent reads its default branch. One repository per Project, and you can change it whenever the work moves.
- 3
Plan
Describe what you need. The agent reads the code while it interviews you, so the Specs land on the product you already have. You never open the repo.
Questions, answered
- Can Plansmith change our code?
- No. The connector is read only. The agent lists files, reads them, and searches on the default branch, and that is the entire surface. It never writes, commits, branches, or opens a pull request.
- Does Plansmith keep a copy of our code?
- Yes, a text copy of the branch you link, so the agent can search all of it. It refreshes when the branch moves and is deleted when you unlink the repository. Through the private-network connector, the copy is built inside your network and then uploaded.
- Who needs to connect GitHub?
- Whoever connects does it with their own GitHub account, and connections are personal. Once a repository is linked to a Project, everyone on the Team plans against it through that connection, so nobody else has to connect. Comment-only teammates read and comment; they do not connect repositories.
- We run GitHub Enterprise Server. Does that work?
- Yes. Register your server's address once, then connect and link a repository the same way. The server has to be reachable over public HTTPS, and registering one is an owner's job.
- Do I need to connect a repository before I start planning?
- No. Plan first and add code context whenever you want it. A plan without it still produces build-ready specs and prototypes. A plan with it produces Specs that fit the product you already have.
Grounded in your repo, not your imagination.
Other code connectors: GitLab · Bitbucket · All connectors