Give each task its own scope
Separate conversations do not automatically share every instruction or decision. State the files, feature, and result each task owns, and identify work that must remain unchanged.
For supported Git workflows, an isolated worktree keeps task changes in a separate checkout. Review shared dependencies and conflicts before combining the results.
Review before combining changes
- Inspect the diff and the checks reported by the task.
- Compare the result with the current project, including edits made since the task began.
- Resolve conflicts and preserve unrelated changes.
- Run checks appropriate to the combined result before using or publishing it.
Applying a change is separate from committing, pushing, deploying, or publishing it. Give the task clear authority for the actions you want. Keep backups of important work.
Local projects and billing workspaces are different
Project files, conversations, and generated reports stay on that computer. Signing in elsewhere does not copy them or merge their data.
A billing workspace selects account entitlements and server records. A local project selects files on your device. Switching one does not automatically move the other.