Skip to content

Name Warp panels from the Start Day launch config and copy resume prompts per panel

  • Date: 2026-11-18
  • Status: Accepted
  • Tags: tooling workflow

Context

Each Warp tab is a separate Claude Code session. close-day needs to know which panel it is in, but the only link between a tab and its panel name was a label typed once per pane with panel.py name --set. A pane with no label made close-day ask every time, and a stale label from an old pane could be picked up by mistake.

start-day also wrote the resume prompts into a document. Luke wanted each prompt on the clipboard as its own entry, so he could paste them into the matching tab.

Decision

  1. The launch config names each panel. claude/warp/launch_configurations/start-day.yaml runs each tab as exec: PANEL_NAME=<Title> claude. panel.py name returns PANEL_NAME when it is set, and records it under that pane's id. A typed --set label still works, and PANEL_NAME wins when both exist.
  2. Resume prompts are per panel, from the freshest handoff. panel.py prompts groups the registry by panel name, takes each name's newest entry, and writes one prompt per panel in Warp tab order. --copy runs one pbcopy per prompt, so clipboard history keeps one entry each.
  3. The install is in the repo. just install-warp-launch-configs copies the config to ~/.warp/launch_configurations/. just install-personal-claude-skills now also copies start-day. Setup steps are in claude/warp/README.md.

Alternatives Considered

Option Why Rejected
Keep typing name --set in each pane Easy to forget, and stale labels pointed at old handoffs.
Match panels by working directory Several panels share ~/repos/work, so the directory does not identify the panel.
Use Warp's tab title from inside the shell No stable way to read it from claude; the title is set by the launch config anyway.
One clipboard entry with all prompts The clipboard holds one value per paste, and each prompt has to go to a different tab.
Edit the Warp config only on the work laptop Luke's home laptop needs the same panels. The config lives in the repo so both can use it.

Consequences

Positive:

  • close-day gets the panel name without asking, in every tab started from Start Day.
  • start-day puts each panel's resume prompt on the clipboard in a single step.
  • Setup on a new laptop is two just commands and a Warp restart.

Negative / Trade-offs:

  • Tabs already open keep their old name until they are reopened from Start Day.
  • The system clipboard holds only the last prompt, so the other five must be pasted from history.
  • The panel list lives in two places: the Warp config and PANEL_ORDER in panel.py. Both must change together (see claude/warp/README.md).
  • The self-test in panel.py already failed on the committed version (resume-prompt assertion). That failure was not fixed in this change.