feat(cli): add a child repo to an existing workspace project
Summary
There is no ao CLI to add a new child git repo to an already registered workspace project.
ao project add --as-workspace only registers a parent folder as a workspace (and adopts the children that already exist at add time). After that, ao project set-config can change branch, env, agents, and similar, but it has no flag or subcommand for workspaceRepos.
ao project get --json shows workspaceRepos (name, relativePath, repo), so the daemon already stores children. The CLI cannot append one.
Why it matters
Workspace projects grow. Example: AgentLab is a workspace (pages, sennight, …). Adding alab-cli later meant cloning onto disk and editing .gitignore by hand. New sessions still will not worktree that child until the project record is updated (desktop UI or store), because there is no:
ao project add-repo --project <id> --path <dir>(or equivalent).
Orchestrators and agents cannot do this from the CLI, which is the surface they actually have.
Current surface (checked)
ao project add/--as-workspace: initial register onlyao project set-config: no workspace-repo fieldsao project ls/get/rm: inspect and delete the whole project- No
ao project add-repo,workspace add, or similar inao --help/ao project --help
Expected
A first-class CLI to attach a child repo to an existing workspace project, for example:
- path (existing git checkout under the workspace root)
- name / relative path
- origin URL (optional; infer from
git remote) - default branch (optional; infer)
It should update workspaceRepos the same way the desktop project settings do, so later ao spawn worktrees include the new child.
Workaround today
Clone the repo into the workspace directory, gitignore it at the root, and hope the desktop UI can register it. No CLI path.
Environment
- AO desktop / daemon used via
aoCLI - Project kind:
workspace - Date: 2026-09-19
Source: Untrivial-ai/agent-orchestrator