Repository navigation
Armonia · Per-agent isolated working copies #1879
Description
Important
Problem — Multiple agents on one shared host would edit the same checkouts. Concurrent edits silently collide and one person's agent can damage another's work.
Approach — Give each agent session its own working copy bound to the session and its owner, and confine its file and shell tools to that copy; changes reach shared branches only through commits and review.
Scope — in: per-session working-copy creation, binding to owner and session, tool confinement, listing, cleanup policy for archived or expired sessions. out: automated merging, cross-site file sync.
Assumptions — Projects are git repositories; sessions carry owner attribution.
Acceptance Criteria
- Starting an agent session in a team project creates or reuses a working copy bound to that session.
- The agent's file and shell tools cannot write outside its working copy except to explicitly granted paths.
- Two agents editing the same file in the same project do not affect each other's copies.
- A person can list their sessions' working copies and their status.
- Working copies of archived or expired sessions are removed only after their unpushed changes are reported, and never while a session is running.
Testing Decisions
Extend the worktree tests and the permission tests for file and shell tools; add a two-agent concurrent edit test.
Key Decisions
- One working copy per session; child sessions get their own unless explicitly sharing their parent's.
- Cleanup never deletes unpushed commits silently.
Constraints & Invariants
- Single-user standalone mode keeps today's behavior unless enabled.
Prior Art
- The engine's worktree support and workspace control plane; open issue fix: New Workspace session hangs — WorktreeState never transitions to ready #1073 (new workspace hangs).
Activity
[-]Team engine · Per-agent isolated working copies[/-][+]Armonia · Per-agent isolated working copies[/+]