Real workflow problems with Cursor agent mode
Cursor agent mode needs a clear workflow before it fits well into everyday development. The desired setup is to create a , open an on a worktree, plan if needed, and then start .
While work continues, the developer wants to switch between other agents as needed. After the work is done, the agent’s changes should be reviewed, approved, or edited file by file.
The worktree should then be merged into the , or the branch should be pushed to a remote , and the worktree should be deleted. The hard parts are seeing changes inside the worktree without opening a separate editor in that folder, and sending changes back without mixing them with changes from other agents.
Key points
- The workflow centers on using Cursor agent mode for real feature work.
- The intended process starts with a and a separate worktree.
- Planning, , review, approval, and merging are all part of the desired flow.
- Viewing worktree changes is awkward without manually opening that folder in another editor.
- Managing several agents can cause changes to mix together.