Launch configurations do not preserve custom pane names

[maxmilian]

Description

Saving a launch configuration does not preserve custom pane names. Panes that were renamed come back as unnamed after relaunching the configuration, falling back to their generated label (New session for a fresh terminal).

Tab titles, tab colors, pane layout, and working directories all survive the round trip — only the pane names are dropped. Normal session restoration (quitting and reopening Warp) keeps them, so this is specific to the launch-configuration path.

Reported by @derekneely in #13898, which covers a different field (tab groups) on the same path; filing separately since it is a distinct field with a distinct fix.

Steps to reproduce

1. Open a tab and split it into two panes.
2. Rename each pane (right-click the pane in the vertical tabs panel → rename, or the pane's context menu). Give them distinct names, e.g. Build and Logs.
3. Confirm the names show in the vertical tabs panel.
4. Save the window as a launch configuration (Command Palette → Save Launch Configuration).
5. Close the window and relaunch the saved configuration.

Expected

Each pane reopens under the name it was saved with — Build and Logs.

Actual

Both panes reopen unnamed, showing New session. The saved YAML contains no pane-name field at all, so the names are lost at save time, not at restore time.

Additional context

• Verified against origin/master at 06e4b74a4.
• The same window saved and restored through ordinary session restoration (quit + reopen Warp) does keep both pane names, which is what makes the launch-config behavior look like a gap rather than an unsupported feature.
• I have a fix in progress and will open a PR referencing this issue.

[oz-for-oss]

@maxmilian

Here's what I found while triaging this issue:

This looks actionable from the provided steps: pane names are preserved by normal session restore but omitted from saved launch configurations. It appears related to the same launch-config snapshot path as #13898, but for a distinct field.

Maintainer details

I concluded that launch configurations drop custom pane names because the launch-config pane template does not serialize or reapply each leaf pane's custom vertical-tabs title..

Triage summary

This is a reproducible client-side launch-configuration bug. The report's observed behavior is that renamed panes round-trip through ordinary session restoration but lose their custom names when the same window is saved and relaunched as a launch configuration.

Evidence

• The issue includes specific reproduction steps and expected/actual behavior.
• LaunchConfig::from_snapshot builds the YAML model from AppState, but PaneTemplateType::PaneTemplate only serializes cwd, commands, is_focused, pane_mode, and shell.
• LeafSnapshot already has custom_vertical_tabs_title, and normal session restoration persists it through SQLite and reapplies it in pane restoration, so the missing behavior is specific to the launch-config conversion/restore path.
• Save and Launch Configuration Template doesn't store Tab groups, all tabs are flat and they are not grouped #13898 is related to the same launch-config snapshot area, but it covers tab groups rather than per-pane names, so this should remain a distinct issue.

Likely fix area

Add a pane-title field to the launch-config pane template serialization/deserialization path, preserve LeafSnapshot.custom_vertical_tabs_title when converting snapshots, apply it when restoring panes from templates, and add launch-config round-trip coverage for renamed panes.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz

[warp-agent-staging]

Oz couldn't complete this task because required inputs, permissions, or resources were invalid or unavailable.

Error Details:
Environment setup failed: Failed to clone warpdotdev-demos/agent-eval-kit, warpdotdev/warp. Check your repository URLs and setup commands.