undefined | Better HN

0 pointsyaskou17h ago0 comments

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?

0 comments

2 comments · 1 top-level

jauntywundrkind15h ago· 1 in thread

Funny you should mention that. Don't hold your breath but I have been doodling with some stuff here.

There's some share .scion space that allegedly your orchestrator / team is I think supposed to be able to share with other tasks, I think... Not sure. No idea how it works. But that's at least some cross worker scratch space... Again allegedly.

verdverm6h ago

I think you should be able to 1. create a shared volume 2. populate that by attaching and running commands/scripts. It should outlive any agent, but not the project.

You might be able to ask an agent, use a skill, or have it done on demand.

I think there are hooks coming that we can tie into. Open an issue on GH, ptone is good about replying, just not timely all the time.

j / k navigate · click thread line to collapse