Docs/The Director/Repositories
Director

Repositories and GitHub

3 min read

Agents work in repositories, so the Director keeps a catalog of yours. Click the pinned Repositories entry at the bottom of the Director's sidebar to open the Repositories view over the session area - every repository under your root folders, with worktrees, branches and changes, in one place instead of a folder hunt every time.

Root folders

A root folder is a directory you keep repos under (for example D:\Repos), and it is what the Director scans to find them. Pick Root folders in the view's left rail to see yours; + Add root folder opens a small dialog with a label, the folder path, and a provider - GitHub, Azure DevOps (with organization and project), or Local Only. The provider is recorded and shown on the root folder; repository rows show a provider inferred from each repository's own origin. Finding them is the folder scan itself - the Director lists the repositories already on disk under each root.

Working with the list

The list itself is a reading surface with two buttons above it - Copy report, which puts this machine's repository state and what to do about it on the clipboard ready to paste into an agent, and Refresh, which rescans your root folders. There is no filter box. The list is one flat list, ordered for you rather than searched by you: repositories with worktrees safe to clear up come first, then those with the most uncommitted changes, then the rest by name - so whatever wants attention is at the top.

Click a repository row and it opens that repository's own screen. A row that is still being checked does not open - its verifying chip says so, and it becomes clickable when the check finishes.

One repository's screen

The header carries a back arrow to the list, the repository's name and address, Open in VS Code, and a Copy report for this repository alone. Under it are five tabs:

  • Changes - the default. Every changed line, stage and unstage per file, and a commit box.
  • Worktrees - the worktrees cut from this repository.
  • Branches - the branches it holds.
  • Pull requests - its open pull requests.
  • History - its commits.
Note
This screen reads and edits a repository; it does not start sessions, and it does not clone. Starting an agent is the New Session window, which is also where you browse to a repository the Director has not seen before.
Note
Prefer the phone? The mobile app starts sessions from the same recent-repo list - see working with sessions from your phone.