Code changes in a folder without a remote
A 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.
What you cannot do yetLink to What you cannot do yet
Workers change code in a fresh copy that the runner clones from the repository's remote. A folder with no GitHub or GitLab remote has nothing to clone. So the folder is planning-only: it shows Not ready, and workers cannot change its code.
What to do todayLink to What to do today
Give the folder a remote. Use one of these:
- Run
agent-runner repo connect --create-github ~/path/to/folder. The runner uses your own GitHub CLI (gh) to create a private repository and push the folder. Then the folder is ready. - Run
gh repo create my-project --private --source . --pushinside the folder. Then connect GitHub in Agent, or runagent-runner repo connectagain.
See Local repositories.
Tell us what you needLink to Tell us what you need
Ask Ava to send this as feedback. The people who build Agent read each request.
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.
- A repository is not readyA repository shows Not ready, or workers can plan but not change code. The repository says why. Here is what each reason means.
- 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.