QodariumA branch for the task
Use a meaningful branch so the intent remains understandable outside the workspace.
Code & reviewProduct preview
Isolated worktrees
Give parallel tasks their own working directories. Keep branches and changes distinct while they remain connected to the same project.
QODARIUM / CODE & REVIEW
YOUR WORK. IN CONTEXT.
On this page
Parallel work needs a little separation
Two agents editing one checkout can easily interfere with each other. Git worktrees provide separate working directories backed by the same repository, making them a useful foundation for independent tasks.
Qodarium's workspace direction connects a session to its working context. The important outcome is simple: you should be able to tell which files an agent is changing and how those changes will come back together.
Separate the work, retain the context
An identifiable directory
Make the worktree path visible before running commands or reviewing a diff.
Independent working files
Reduce accidental interference between tasks that need to change different parts of the same repository.
A deliberate integration step
Review, test and merge through your normal Git workflow. Isolation does not replace integration.
What worktrees do not isolate
Worktrees separate checked-out files. They do not automatically isolate ports, databases, shared caches, credentials or external services. Parallel tasks can still compete for those resources.
Use unique development ports and task-specific test data where needed. See the worktree field guide for a practical mental model.
A few good questions
Are worktrees disposable sandboxes?
Not by themselves. They are Git working directories, not a security boundary.
Will Qodarium merge automatically?
Do not assume automatic merging. The intended workflow keeps review and acceptance explicit.
A little less watching. A lot more building.Make room for
Make room for
long-running ideas.
A workspace that holds the context while you focus on what comes next.
IN DEVELOPMENT · COMMUNITY + TEAM