One instrument. One useful task.
Give parallel tasks explicit boundaries
Step 1: Two campaigns collide
Separate clones provide independent working files. In a shared checkout, assign explicit file ownership.
Still frames · every step is available
“Give parallel tasks explicit boundaries.”
Separate clones provide independent working files. In a shared checkout, assign explicit file ownership.
See who does what
Choose the task, workspace and permitted scope.
Separate clones provide independent working files. In a shared checkout, assign explicit file ownership. Start here: Separate clones → separate workspaces.
Ask each agent to identify its working directory, branch and permitted files.
Agents can share a checkout. Create separate clones when tasks need isolation.
Copy an example instruction
Illustrative task shared across these lessons. Adapt the scope and file ownership to your project. Try the complete example and inspect its tests →
Add a saved-filter control. Keep the change focused. Inspect the existing filtering behaviour, implement the control, and run the relevant checks. Ask a separate agent to review the diff without editing it. Collect its findings and resolve confirmed issues before proposing a commit.
Before you start
Use a Git repository with a committed starting point. Decide whether agents are collaborating on different files or producing alternative implementations of the same change.
Illustrated explanation · The scene explains the workflow. Follow the guide to perform it in the app.
About this demonstration
Instructions reviewed against product 1.5.119. Authored illustration; no application execution is claimed.