Repository navigation
Replies: 1 comment 2 replies
|
Thanks again, @smota, for the open question and for setting out both sides. As you describe it, several builder agents in one rig work on the same repository at once, so AgentFlow's dispatch creates a git worktree per work item, points the agent at it and removes it after merge, while the rig doesn't know the directory is a worktree or when it should go. You ask whether we've considered worktree management, whether it fits as infrastructure or belongs to the layers above, and, if it's out of scope, whether there's a pattern for a layer above to tell the rig it manages that directory. It's with the team, and the fit answer will come here. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi, an open question rather than a request. I'd like to know whether you've thought about this and how it fits OpenRig's vision.
Context
I'm designing an optional OpenRig execution layer for AgentFlow, an SDLC framework for agent teams. AgentFlow decides phases, gates and evidence; the rig runs the seats. One rig points at one project.
Several builder seats work on the same repository at once, each on a different issue. To stop them trampling each other, each seat needs its own git worktree and branch.
As far as I can tell, a rig spec lets me set a seat's working directory, but has no notion of a worktree. If I've missed something, please point me at it.
Workflow today
git worktree addfor that item.This works. The rig is simply unaware that the directory is a worktree, who created it, or when it should go away.
The idea, loosely
An optional per-seat setting saying "this seat runs in its own worktree of the rig's repository", with OpenRig handling creation, pointing the seat at it, and safe removal. Off by default.
Pros
.gitbeing a file) and Move an existing seat to a new working directory and resume the same conversation there #1525 (moving a seat to a new directory) suggest these edges already show up.Cons
Where I'm torn
On one hand, this looks like it belongs to the layers above OpenRig. Which branch, when to clean up and what counts as "done" are workflow decisions, and I'm keeping them in AgentFlow for now.
On the other hand, optional per-seat worktree isolation could strengthen OpenRig as an infrastructure layer: "each seat gets an isolated workspace" is a mechanism, and the policy could stay above it.
Questions for maintainers
Thanks.
All reactions