Summary

Tab Configs are a great addition — they auto-execute commands on open (a major improvement over legacy launch_configurations YAML). But they're UI-only: accessible only via the + menu. There's no CLI flag, URI scheme, or IPC for programmatically opening a specific Tab Config.

Request

Expose Tab Configs via a programmatic trigger. Two reasonable options:

1. URI scheme: warp://action/open_tab_config?name=my-config
2. CLI flag: warp.exe --tab-config my-config (or similar; the existing warp.exe binary is the Oz CLI today, so maybe a separate terminal-launch flag)

Either would suffice.

Why this matters

The command-execution primitive already exists in Tab Configs — commands run automatically when a tab opens via the + menu. The only thing missing is a way to trigger that open from outside the UI.

Related: #3959 (open tab and execute a command from CLI) has been open since 2023 and is the broader ask. This feature request is a tighter, more achievable ask since the plumbing for command execution is now in place — you just need to expose an external trigger.

Use case

Multi-session workflows where I want to programmatically launch terminal sessions with specific configurations (working directory, pre-run commands, pane splits) from a script or shortcut. Today I'm using cmd.exe + schtasks /it to open cmd windows, which isn't integrated with Warp at all. If I could trigger Tab Configs from a URI or CLI, I could keep everything in Warp.

Tested

Confirmed the following do NOT work in v0.2026.04.08.08.36:

• warp://action/open_tab_config?name=X — no-op
• warp://action/new_tab?config=X — opens a blank tab, ignores the parameter
• warp://action/split_pane?direction=right — no-op
• warp.exe CLI: only exposes Oz cloud agent commands, no terminal/tab management

Only warp://action/new_tab (no parameters) and warp://action/new_tab?path=X are functional.

Session: Dozer (5d3a) | Task: 6g3fqhCpRWVvMFJG