project

# Project Manage the local multi-repo registry (`~/.ai-workspace/repos/` and `projects/` symlinks) so swarms and agents can target any repo by name, not path. ## When to use - User says "clone X", "add repo Y", "list projects", or references `owner/repo` without a local path. - Swarm needs `--workspace /path/to/repo` that isn't yet cloned. - Workspace context shows missing `projects/` symlink for a repo referenced in a prompt. ## Prerequisites - `agent-toolkit` with `project` subcommand (`agent-toolkit project --help`). - `gh` authenticated for private repos (`gh auth status`). - Workspace has `repos/github.com/<owner>/<repo>` layout. ## Workflow ### 1. Clone and index ```bash agent-toolkit project clone owner/my-repo # clone + symlink projects/my-repo -> repos/github.com/owner/my-repo agent-toolkit project clone owner/my-repo --branch feat/x # Alias resolution: swarm's config.py also resolves_owner_repo from prompt URLs like https://github.com/owner/repo # Verify agent-toolkit project list # indexed projects ls -l ~/.ai-workspace/projects ls ~/.ai-workspace/repos/github.com/owner/my-repo ``` ### 2. Use with swarm and other skills ```bash # Swarm can target any indexed repo via --workspace agent-toolkit swarm start --recipe pair --ui herdr --runner opencode --model-profile balanced --workspace ~/.ai-workspace/repos/github.com/owner/my-repo --attach "task" # Inside a cloned repo, just run from its directory — swarm's find_repo_root u...