Save a two-agent project default

Before you start

Use a build containing complete Saved Views. Both accounts must exist in the current catalog. Finish active turns before applying a different saved layout. A Saved View stores configuration, not prompts, transcripts or authentication.

Save and assign the layout

1. Select the project and arrange two panes. Choose each pane's view, provider, account, model, effort, mode and workbench choice. Arrange the complete chat/file tab order, including the original chat, and select the tab to show.
2. Open Saved Views... from the window menu or command palette. Choose Save current view... and name the layout.
3. Inspect both configuration summaries, then choose Set as project default.
4. Leave and reopen the project. Confirm both configurations and the split direction/divider restore. The complete saved tab order is restored automatically only when that pane has its original chat alone; otherwise its existing tabs stay in place.

Open or remove the default

Use Open to apply a saved view manually. Manual application restores the complete saved tab order and configuration in the affected panes, replacing tabs not present in that layout; finish active turns and save file edits first. Use ordinary default view clears the default assignment without deleting the saved view.

Expected result and recovery

A Saved View includes the complete displayed order and selected tab, with up to twenty-one chat/file tabs per pane. The original chat can be reordered, and a layout can start with a file or contain only files. Each saved chat keeps its own configuration. Newly created chat slots start fresh; an existing chat reused while applying the layout may retain its conversation. Saved Views do not clone or resume sessions; earlier conversations remain in History where supported. File tabs store project-relative paths, not edited file contents. An older view without tab data leaves current tabs alone; re-save it to capture them.

A legacy layout must be re-saved before becoming a default. Missing accounts, missing projects and active turns can block application; the app must not silently substitute another account. Unreadable/newer storage is retained and saving is disabled. Preserve that data and inspect the error rather than repeatedly overwriting it.

Restoring a layout does not mean a foreign session was resumed. See reviewed context handoff for continuity across engines.