Add warp://tabconfig/<name> deeplink

[haha1903]

Description

Add a warp://tabconfig/<name> URL scheme handler so users can launch a saved tab config straight from a deeplink (alongside the existing warp://launch/<name>).

By default the tab config opens as a new tab in the active window. Pass ?new_window=true (or invoke when no Warp window is open) to open in a brand-new window instead.

<name> matches the tab config's name field case-insensitively, falling back to the file stem so both warp://tabconfig/My%20Tab and warp://tabconfig/my_tab.toml work.

The handler dispatches to the existing Workspace::open_tab_config, so the params modal and worktree branch generation flows are reused unchanged.

Gated on the existing FeatureFlag::TabConfigs.

Why

Lets users (and external tools / scripts / browser bookmarks) jump straight into a configured pane layout without going through the + menu. Mirrors the long-standing warp://launch/... deeplink for launch configs.

How

• New UriHost::TabConfig variant in app/src/uri/mod.rs, parsed from tabconfig host string and listed in validate_custom_uri's allowlist.
• New handler handle_tab_config_uri that resolves the config and either reuses the active window's workspace or opens a new window (via open_new_window_get_handles), then calls workspace.open_tab_config(...).
• Workspace::open_tab_config promoted from private to pub(crate) so it can be invoked from the URI handler.
• Added a wasm-side stub for load_tab_configs so the cross-platform pub(crate) use imp::load_tab_configs; in user_config/mod.rs matches the pattern already used by load_launch_configs (no cfg gate needed).

Testing

Manual:

• open "warposs://tabconfig/<name>" opens the config as a new tab in the focused window.
• open "warposs://tabconfig/<name>?new_window=true" opens it in a new window.
• Tab config with params triggers the existing params modal.
• Worktree-style tab configs still get an autogenerated branch name.
• Unknown <name> logs a warning and is a no-op.

cargo fmt and cargo clippy --workspace --all-targets --all-features --tests -- -D warnings both pass locally. Full ./script/presubmit will run on CI.

Server API dependencies

No server changes.

Agent Mode

• Warp Agent Mode - This PR was created via Warp's AI Agent Mode

Changelog Entries for Stable

CHANGELOG-IMPROVEMENT: Added a warp://tabconfig/<name> deeplink that opens a saved tab config in the active window (or a new one with ?new_window=true).

[cla-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @haha1903 on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment @cla-bot check to trigger another check.

[haha1903]

@cla-bot check

[cla-bot]

The cla-bot has been summoned, and re-checked this pull request!

[oz-for-oss]

@haha1903

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

You can view the conversation on Warp.

I requested changes on this pull request and posted feedback.

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

Powered by Oz

[oz-for-oss]

Overview

This PR adds a warp://tabconfig/<name> handler that resolves local tab configs by display name or source file stem and opens them in an existing or new workspace.

Concerns

• The URI window-behavior hint can create a fallback window before the tabconfig handler sees ?new_window=true, which can violate the documented default/new-window behavior on platforms that cannot activate the existing window.
• Security pass: no additional security findings beyond the window-selection behavior noted inline.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

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

Powered by Oz

[oz-for-oss]

⚠️ [IMPORTANT] window_behavior_hint() is resolved before handle_tab_config_uri can inspect ?new_window=true; on Linux/Wayland this W::default() fallback can create a window up front, so no-query links may ignore the existing window and new_window=true can produce an extra empty window before the tab config opens. Move the new/reuse decision into the handler or use a hint that cannot pre-create a window.