Sessions
Every session is an isolated branch of your project. It gets its own dedicated git branch, its own chat thread, and its own sandbox — so an experiment in one session can’t break another. The tab bar above the chat shows your sessions. Main is always first; every other session is a fork.Create a session
- Click + New session in the tab bar (forks from your current session), or
- Use the slash command to fork and hand the new session a task in one step:
/sprint <feature> also launches its custom sprint in a new session, keeping your current session free.
Sessions require the project to be connected to GitHub — each one lives on its own branch. There’s a cap on active sessions per project; archive an unused one if you hit it.
Work in parallel, merge back
Run different tasks in different sessions simultaneously — a feature in one, a refactor in another — then bring the work together:1
Merge into Main
Open a session’s menu (▾) and choose Merge into Main. pre.dev opens a pull request and auto-merges it when it’s clean.
2
Conflicts? Let the agent resolve them
If the merge conflicts, you’ll see the PR link plus a Let agent resolve button. The agent in Main picks up the conflict markers, resolves them, commits, and pushes — or you can resolve on GitHub yourself.
3
Or promote a session to Main
If a fork became the real project, choose Make this the Main instead of merging. The session becomes Main — including taking over the project’s live preview URL.
Archive and revive
Done with a session? Archive it from the menu — it leaves the tab bar but its git branch is preserved, so you can Revive it later from the Archived dropdown and pick up exactly where it left off.Working with teammates
Sessions are multiplayer. Presence avatars on each tab show who else is viewing that session right now, and session changes (create, rename, archive, promote) sync live to everyone in the project. Double-click a fork’s tab to rename it (Main keeps its name).Parallel agents
Within a single sprint, the agent can fan independent tasks out to multiple sub-agents in one wave — for example, building three unrelated components at the same time instead of one after another. When this happens, a live panel appears in the chat feed:One tab per agent
Each sub-agent gets a tab showing its objective, live status, and tool count. Switch tabs to watch any of them work.
Full inspectability
Every tool call inside a branch is a click-to-expand card — search results, command output, and file diffs, same as the main feed.
Files touched
A strip at the top of each branch lists every file that agent wrote or edited.
Conclusions
When a branch finishes, its summary and findings appear in a conclusion box — including a pass/fail verdict for verification branches.
When to use which
What’s next?
Build Modes & Effort
Control what each session builds and how deep sprints go.
Collaboration
Invite teammates and control project access.