yaskou

Yeah, that's the fun part. Probably built first for exporting monolith slices to OSS, but the reverse direction is more interesting to me. Tracking an upstream or keeping a private fork in sync. That's what makes Copybara useful well beyond the monorepo use case.

Cool, I only found Scion recently, so I may be missing a lot. The sandboxing part looks nice to me, and I like that there is some message-bus-ish thing between agents.

One thing I keep getting stuck on with these systems though: they all seem to assume an agent lives in one worktree of one git repo. Maybe that is fine in a monorepo world. Outside of that, the repo boundary is often just not the task boundary. Some context lives next door, or two repos away, and the sandbox somehow has to know what to bring in.

I'm wondering if there is a tool in the agent orchestration space that prepares multi-repository worktrees for a subagent out of the box?

How do you manage the lifecycle of the worktrees in practice? Is it mostly manual git worktree add/remove, or do you use aliases/scripts/some other tools?