Parallel Development Workflow
The core power of Omniscribe is running multiple AI coding assistants simultaneously, each working on a different aspect of your project. This guide walks through a practical workflow for getting the most out of parallel sessions.
Example Workflow
Imagine you need to add a new feature that touches the backend, frontend, and tests, while also fixing an unrelated bug. Instead of tackling these sequentially, you can run all four tasks in parallel.
1. Open Your Project
Launch Omniscribe and open your project from the welcome screen or recent projects list.
2. Create a Multi-Session Layout
Press Shift+N to open the launch presets modal. Select the 2x2 grid preset to create four session slots at once. You can also create sessions one at a time with N.
3. Assign Branches to Each Slot
If you have worktree mode set to "Branch" in Settings > Worktrees, each session slot can target a different git branch. This gives each AI assistant its own isolated working directory, preventing merge conflicts between sessions.
Configure the four slots:
| Slot | Branch | Task |
|---|---|---|
| 1 | feat/api-endpoints | Backend API work |
| 2 | feat/frontend-ui | Frontend UI implementation |
| 3 | feat/tests | Writing tests |
| 4 | fix/bug-123 | Bug fix |
4. Launch All Sessions
Press L to launch all sessions simultaneously. Each session opens in its own terminal pane within the grid layout.
5. Give Each Session Its Task
Click into each terminal and provide the AI assistant with its instructions. Be specific about the scope of work for each session so they do not overlap.
6. Monitor Progress
Watch the status indicators on each terminal header:
- Working -- the AI is actively coding
- Idle -- the AI has finished its current task and is waiting
- Needs Input -- the AI is asking you a question and waiting for your response
- Error -- something went wrong
Focus your attention on sessions showing "Needs Input" since those are blocked until you respond.
7. Commit and Push
Use quick actions from each session's terminal header menu to commit and push changes. The "Commit & Push" quick action handles the common git workflow in one click.
Tips for Effective Parallel Development
Use Worktree Mode "Branch"
When worktree mode is set to "Branch" in Settings > Worktrees, Omniscribe creates a separate git worktree for each session's branch. This means each AI assistant works in its own directory with its own branch checked out, completely avoiding conflicts between sessions.
Resume Sessions After Breaks
If you need to step away, your session history is preserved. Open the session history panel with Ctrl+H (or Cmd+H on macOS) to browse, search, and resume any previous session. The "Continue Last" button quickly picks up where the most recent session left off.
Stop All Sessions at Once
When you are done, press Cmd+K (macOS) or Ctrl+K (Windows/Linux) to stop all running sessions. This cleanly terminates all PTY processes.
Watch for "Needs Input" Status
Sessions that need your input are blocked and cannot make progress until you respond. Check the status indicators regularly and prioritize responding to these sessions to keep all lanes moving.
Use Drag-and-Drop to Organize
Drag terminal panes by their grip handle to rearrange the layout. Put the sessions you are monitoring most closely in the most visible positions.
Rename Sessions for Clarity
Double-click a terminal session title to rename it. Use descriptive names like "Backend API" or "Bug #123" so you can quickly identify each session's purpose at a glance.