A repository is not ready
A repository shows Not ready, or workers can plan but not change code. The repository says why. Here is what each reason means.
Reasons and fixesLink to Reasons and fixes
- "This folder has no remote, so workers cannot change its code yet." Run
agent-runner repo connect --create-githubin the folder to put it on GitHub, then connect GitHub. See Code changes in a folder without a remote. - "To let workers change the code and open pull requests, connect GitHub (or GitLab)." The folder has a GitHub or GitLab remote, but Agent has no access. Connect GitHub or GitLab and give it access to that repository.
- "Workers change code only in GitHub or GitLab repositories." The folder has another kind of remote. Move it to GitHub or GitLab.
- The computer is offline. The runner has not been seen for 7 days. Start the runner on that computer.
- "The local runner is off for this organization." An admin turns runners on.
- "The runner was removed." Sign the runner in again with
agent-runner login, then runagent-runner repo connectin the folder. - "The connection is not finished yet." Finish the GitHub or GitLab connection, or start it again.
The list updates by itselfLink to The list updates by itself
In setup, the repository list checks again every few seconds.
Checked against the product on 2026-10-05.
Was this helpful?
Related articles
- Local repositoriesConnect a Git folder on your computer through the runner. Work on it runs on your computer with your own git access. A folder needs a GitHub or GitLab remote before workers can change its code.
- GitHub and GitLabConnect GitHub or GitLab and choose the repositories Agent may use. Workers then read the code, change it and open pull requests or merge requests.
- Code changes in a folder without a remoteA folder with no GitHub or GitLab remote is planning-only. Workers can read about it, but they cannot change its code. Add a remote to fix it.