Feature · Knowledge
Repository Atlas
Explore each repository through its files, rules and architecture.
How it works
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 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 stored
Only derived facts: paths, names, versions and counts. Not file contents.
Who can do what
Viewers can browse. Members can add repositories.
From the help article Repository Atlas, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewerlistAtlasRepositoriesLists atlas repositories.
Types:
Record<string, never>returns{ items: AtlasRepositorySummary[]; settings: AtlasSettings }
ViewergetAtlasRepositoryGets the atlas repository.
Types:
{ id: string; scanId?: string }returns{ repository: AtlasRepositorySummary; scan: AtlasScanRef; profile: AtlasProfile; history: AtlasScanRef[]; findingWork: …
ViewerdiffAtlasScansCompares atlas scans.
Types:
{ id: string; fromScanId: string; toScanId?: string }returns{ from: AtlasScanRef; to: AtlasScanRef; diff: AtlasProfileDiff }
MembersubmitAtlasProfilesSubmits atlas profiles.
Types:
{ profiles: AtlasProfile[] }returnsAtlasSubmitResult
AdminremoveAtlasRepositoryRemoves the atlas repository.
Types:
{ id: string }returns{ removed: boolean }
ViewergetAtlasWorkOverlayGets the atlas work overlay.
Types:
{ workItemId: string }returnsAtlasWorkOverlay
ViewerprobeAtlasRepositoryChecks the public health routes the latest profile names. Results are cached for a minute.
Types:
{ id: string }returns{ probes: AtlasProbe[]; targets: number }
AdminNo API tokensupdateAtlasSettingsAdmins turn the platform's own refresh (a scan of each checkout it prepares for work) on or off.
Types:
{ autoRefresh: boolean }returnsAtlasSettings
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
MembercreateWorkItemCreates a work item.
Types:
CreateWorkItemRequestreturnsWorkItemDetail
MembergetWorkLaunchReadinessGets work launch readiness.
Types:
{ workerId?: string; templateId?: string }returnsimport('./execution.js').WorkLaunchReadinessDto
Screens
/atlas/atlas/:repositoryId
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Policy changed
- Atlas repository removed
- Atlas scan recorded