Local repositories

After you sign the runner in, and each time it starts, it looks for Git folders so setup can offer them. Nothing connects until you choose it.

• It looks in ~/code, ~/src, ~/dev, ~/projects, ~/repos, ~/workspace, ~/Documents/repos, ~/Documents/GitHub, ~/Developer and ~/GitHub, two levels deep.
• It sends only facts: the name, the folder under your home folder, the remote without any password, the default branch and the last commits. Never file contents.
• Only you see your folders in Agent.
• Start the runner with --no-discover to turn this off.

Run this in Terminal on the computer with the runner:

agent-runner repo connect ~/path/to/your/repo

Without a path, it connects the current folder. agent-runner repo list shows what this computer connected.

A folder with no GitHub or GitLab remote is planning-only. The CEO can plan work on it, but workers cannot change its code. Agent says this plainly on the repository.

To fix it, give the folder a remote:

• Run agent-runner repo connect --create-github ~/path/to/folder. With the GitHub CLI (gh) signed in, the runner creates a private GitHub repository and pushes the folder. Add --public for a public one. Without the flag, the runner asks first (default no).
• Or run gh repo create my-project --private --source . --push in the folder, then connect GitHub in Agent.

Workers can plan on it at once. To let them change the code and open pull requests, connect GitHub or GitLab and give it access to that repository.

Workers change code only in GitHub or GitLab repositories. A folder with another remote stays planning-only.