Document tab groups in legacy launch configurations

[bholmesdev]

Summary

• Document that saving a Launch Configuration preserves tab group metadata and membership.
• Add the tab_groups and per-tab group YAML fields, supported group properties, a complete example, and membership constraints.
• Keep Tab Configs out of scope because their single-tab TOML schema does not support tab groups.

Content design plan

• Reader and job: A Launch Configuration user saving grouped tabs or editing legacy YAML who needs the groups to reopen correctly.
• Gap today: The page documents windows, tabs, and panes but not how grouped tabs are saved or represented in YAML.
• Change: Add a focused Tab groups reference and example. Exclude Tab Configs because they use a separate single-tab schema without group membership.

Related issues

• Depends on Save and restore tab groups in launch configurations warp#14624
• Fixes documentation coverage for Save and Launch Configuration Template doesn't store Tab groups, all tabs are flat and they are not grouped warp#13898

Validation

• npm run typecheck
• npm run build
• git diff --check
• npm run lint not run because Trunk is not installed locally.

Screenshots

Not applicable; this changes YAML reference content only.

Follow-ups

Merge after warpdotdev/warp#14624 ships.

Co-Authored-By: Warp agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 8, 2026 5:21am UTC

[warp-for-oss]

@hongyi-chen

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

Overview

This PR adds tab group reference content to the legacy Launch Configurations page, including saved UI behavior, the tab_groups and per-tab group YAML fields, a complete grouped-tabs example, and membership constraints.

Concerns

• No blocking concerns. Because the documented behavior depends on warpdotdev/warp#14624, this should merge only after that product change is available in the shipped Warp build.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz