Move several goals forward in parallel
Open several Conversations in split panes, each keeping its own goal, context, and tool state. You can wait for an approval or a long task in one pane while investigating another problem in a second pane.
Split panes
Open several conversations in one window, ideal for moving bugs, features, and research forward in parallel.
A multi-project view
Conversations from different project folders can work side by side without switching the whole workspace.
Visible status
Work that needs attention, is running, or was recently continued is gathered in one place, so you watch the screen less.
Checkpoints and replay
Save checkpoints at key turns. When you want to compare approaches, undo an unsatisfactory change, or restart from a stable state, review the history and return to an earlier conversation and code state.
Save before a stable result
Create a checkpoint when tests pass, a review is confirmed, or you are about to try a risky change.
Compare instead of guessing
Review changes, tool results, and conversation history to identify which step introduced the problem.
Return to the checkpoint and continue
After rolling back, the project boundary and team identity remain, and you move forward from a known state.
Important projects should still use version control and backups. Checkpoints restore state for Agent workflows; they do not replace a repository's commit history.
Tasks, results, and handoff
LoneAct records tasks, run status, tool results, and final deliverables separately, which makes it easier to continue work or hand it to someone else for review.
| Object | What it keeps | How to use it |
|---|---|---|
| Task | Goal, status, dependencies, and acceptance criteria | See what the team is moving forward and avoid duplicate work |
| Run | Model, tools, approvals, and results | Find which step a failure came from |
| Artifact | Files, branches, reports, or external links | Review directly or continue delivery |
| Memory | Project facts, preferences, and long-term agreements | Let later conversations follow the same context |
Three principles for keeping parallel work under control
One goal per pane
Do not pack unrelated goals into one conversation; the more mixed the context, the harder approval and review become.
Write key moments back to the conversation
Ask the Agent to state the current conclusion, open items, and next step in one sentence so you can switch back easily.
Verify before widening
Validate models, tools, and team configuration on a small task first, then apply the same structure to larger work.