Repository navigation
Replies: 3 comments
|
If the lock is applied to the whole Even if the agents currently modify different files, sharing the same workspace can become risky if they later touch common metadata, git state or temporary files. If this helped, please mark the answer as accepted so it can help others too. |
|
On the merge-afterwards part: separate files don't mean the outputs can't break each other. One agent renames a function in That's a synthetic test case, so it shows it can happen, not how often. On a real repo (lukeed/mri) I got the same thing with both agents in one file: each branch passed So if you go the separate-worktree route, run your tests once on the merged result before it replaces anything. I build Pytxo, and |
|
There is now a built-in option for this: set the local-directory resource to For an existing resource: multica project resource list <project-id>
multica project resource update <project-id> <resource-id> --execution-mode worktreeChoose the A few constraints matter here:
For multiple agents editing the same physical working directory directly, I checked the current resource guide and CLI examples against the daemon's worktree lock handling; this is based on the documented/current implementation, rather than a reproduction of your particular runtime setup. |
Uh oh!
There was an error while loading. Please reload this page.
I have a batch of independent files, each assigned to a different agent. The agents work on separate files, so their outputs won’t overlap or overwrite one another. However, runs using the same
local_directoryresource are serialized by a path lock.Is there a supported CLI option or resource setting to disable or otherwise avoid this lock for non-conflicting work?
All reactions