Multi-Repo Sessions

Note

Multi-repo sessions are a Buck feature. Dolly and Pearl do not dispatch EKS session pods.

Multi-repo sessions allow Bucky to work across multiple repositories simultaneously. This is useful for tasks that span services — like updating a shared API contract, coordinating a migration, or investigating a cross-service issue.

How it works

Multi-repo is a native capability of run_claude_session, not a separate mechanism:

1. The agent’s run_claude_session tool accepts a repos array — a single entry for single-repo sessions, multiple entries for multi-repo
2. The PodOrchestrator creates an EKS pod that clones all specified repos into the workspace
3. Claude runs with awareness of the multi-repo layout and full access to all repos
4. Results are reported back via pod-bound JWT auth, the same as single-repo sessions

The only difference between single-repo and multi-repo sessions is the number of entries in the repos array. There is no separate dispatch type, workflow, or tool — it’s all handled by the same EKS pod infrastructure.

Caution

Multi-repo sessions do not install dependencies for individual repos. Claude has access to the source code but cannot run project-specific build/test commands unless the tools are already globally available in the session pod image.