Chat is not one session. It is a set of tabs, and each tab is its own agent.

## One workspace, several engines

Open a tab for Claude Code, another for Codex, another for Grok. They run at the same time, on the same workspace, each with its own conversation and its own run state, so the tab strip tells you which ones are working and which are waiting on you.

They run under **your** subscriptions, on the engines you already installed. Pathrule is not reselling model access; it is running the tools you already have, side by side.

## They all start from the same knowledge

This is the reason running two engines is useful rather than just noisy. Every tab receives the same path-scoped memories, rules and skills for the path it is working in.

So a second opinion is genuinely a second opinion: another engine reading the same context and the same constraints, not a fresh session you have to explain your product to again.

## Tabs survive a workspace switch

Open tabs are tracked above the workspace they belong to. Switch to another workspace and its own tabs appear; switch back and yours are still there, still running. A long job does not end because you looked at something else.

## Parallel work without collisions

Two agents editing one repository is a merge accident waiting to happen, so parallelism is paired with isolation: any session can run in [its own branch and its own checkout](/docs/studio/isolated-branches), which is what makes "several agents at once" a working arrangement rather than a race.

On the Tasks board the same idea is automatic: [parallel runs](/docs/studio/board-settings#parallel-runs) put groups that touch different files in separate worktrees and merge colliding groups into one sequential lane.

## Or let Auto decide

If you would rather not pick, [Pathrule Auto](/docs/studio/pathrule-auto) chooses the engine and the model for you, and stays on one engine per thread because moving is a real context handoff.