Start with one working project
Open the repository in Lattice and check its current branch and uncommitted changes. Start a separate terminal session for each coding CLI. Both tools use your own configured accounts; installing Lattice does not include a provider subscription or extra usage.
Before assigning work, run the smallest relevant check yourself. A known failure is part of the starting state. Record it so the agents do not mistake it for a regression they introduced.
Divide by responsibility, not by enthusiasm
For a contained bug, give one agent the implementation and ask the other for a read-only diagnosis or review. If both need to edit, use separate branches or worktrees, and give each a different set of files. Two writers changing the same checkout can overwrite assumptions even when Git reports no conflict.
Make the handoff between roles explicit. A reviewer should know the behavior being changed, the acceptance criteria, and which diff to inspect. Asking two agents to ‘fix it’ creates duplicate work and an unclear result.
Goal: reopening a saved project preserves its active terminal.
Implementation: session restore code only.
Review: inspect the diff and look for missing-state cases; do not edit.
Done: reopen works with zero, one, and several saved terminals.
Before merging: review the diff and run the restore checks.Share the decisions that affect the work
Keep a short project brief with the goal, important constraints, known failures, and decisions already made. Link to source files instead of copying whole files into the brief. Update it when a decision changes.
Lattice’s memory integration varies by agent. Claude Code has full memory support. Codex needs a one-time hook approval, while Gemini and Cursor have partial support. Confirm the context reached the session before relying on it.
Bring the results together deliberately
Review one change at a time. Read the diff, check the reported commands and their exit status, then test the combined behavior after integration. A successful check on one branch does not prove that two changes work together.
On supported platforms, Lattice also offers paired Claude/Codex research for read-only investigations. It is separate from editing with two terminal sessions and is unavailable in the Windows beta. Phone access is still in development.
Keep the workflow in one place.
Explore Lattice’s desktop workspace, supported integrations, and platform details.
View Lattice