Repository Atlas
The Atlas shows the stack, infrastructure, rules and architecture of each repository, measured from its files and Git history. No model writes these facts.
What it showsLink to What it shows
Repository Atlas has three views: Repositories, Stack matrix and Portfolio map. Each repository shows its languages, stack, readiness and last commit.
How a repository gets profiledLink to How a repository gets profiled
agent-runner repo connectuploads a profile of the folder.--no-atlasskips it.agent-runner atlas scan --discover ~/code --uploadprofiles many folders at once.- Upload a profile file takes the JSON file that
agent-runner atlas scan --jsonwrites. - Refresh automatically: when a worker's task prepares a repository, the platform scans that checkout. Local repositories are never scanned this way. Only admins change this.
What is storedLink to What is stored
Only derived facts: paths, names, versions and counts. Not file contents.
Who can do whatLink to Who can do what
Viewers can browse. Members can add repositories.
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.
- The local runnerThe runner is a small program on your own computer. It starts your own Claude Code or Codex, under your own sign-in, for work that you asked for.
- 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.