2solarmax

Pane Resume — Development skill for Claude Code

Development community

Put your agents back in the panes they were in.

How to install Pane Resume

This entry records only its repository, not the path inside it, so there is no exact command to give. Open 2solarmax/pane-resume and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Pane Resume does

Put your agents back in the panes they were in. After a Mac restart, Warp and Superset restore your panes as idle shells — this resumes the Claude Code / Codex / Gemini conversation each pane had. Opt-in zsh hook, macOS.

Alternatives in Development

WARP.md — This file provides guidance to WARP (warp.dev) when working with code in this repository 10.5k ★
Investigate Performance — Investigate a Nimbalyst performance problem (freeze, lag, idle CPU, slow op, memory growth) with measured evid 1.6k ★
Claude Auto Resume — A shell script utility that automatically resumes Claude CLI tasks when usage limits are lifted 732 ★

README

pane-resume

Auto-resume your terminal's agent conversations after a **full Mac restart**. Supports **[Warp](https://warp.dev)** and **[Superset](https://superset.sh)**.

**One pane per conversation.** A conversation lives in several panes over its life — resumed, reopened, moved. Every pane keeps a durable record of it, so after a crash they would *all* restore it, and two copies appending to one transcript interleave it into nonsense. Before launching, a pane atomically claims the conversation (`resuming//`) and checks no agent is already running it; whoever claims first restores it and the rest stand down and say so in the log. Claims are namespaced per terminal run and the previous run's are reaped on the way in — a claim from the run that just crashed must never refuse the restore it exists to enable.

Both terminals restore your windows/tabs/panes and their working directory when you relaunch — but after a *machine restart* they bring each pane back as an **idle shell**, with the Claude Code / Codex / Gemini conversation that was running in it gone. This tool bridges that gap: when a pane comes back, it resumes the exact session it had.

Why a restart loses sessions (and closing the app doesn't)

Your agent runs as a live process attached to the pane's PTY. Closing the app window usually leaves that process (and its terminal daemon) running, so reopening re-attaches. A **machine restart kills every process**, so the layout and scrollback are restored from disk but the conversation isn't — nothing on disk says "pane X was running conversation Y."

Warp is explicit about this: session restoration brings back panes and working directories, not running processes ([docs](https://docs.warp.dev/terminal/sessions/session-restoration/); see also [#10583](https://github.com/warpdotdev/warp/issues/10583), [#9416](https://github.com/warpdotdev/warp/issues/9416)). Superset has the same gap, tracked in [#3496](https://github.com/superset-sh/superset/issues/