← ClaudeAtlas

supercompact-selflisted

Supercompact this conversation in place — keeps the same session id and name, after saving a full copy for safekeeping.
SignedAdam/ClaudeSessions · ★ 3 · AI & Automation · score 75
Install: claude install-skill SignedAdam/ClaudeSessions
Supercompact the conversation we are in right now, in place. Arguments given: `$ARGUMENTS` Pass `--tools` if I said `tools`. Pass `--relaunch` unless I said `stay`: ``` claudesessions compact --current --in-place --relaunch [--tools] ``` Then tell me, in four lines or fewer: 1. the before → after size and message count 2. the session id and title of the safekeeping copy 3. whether it handed off to my relaunch script, or the `cd … && claude --resume …` command if it did not — note that it is the **same** session id I am already using 4. that this window still holds the old context Do not summarize the conversation yourself and do not run any other command. ## What it does differently from `/supercompact` `/supercompact` forks: the compacted conversation gets a new session id, and I move to it. This one keeps the id and the name, so I can carry on under the same identity. Before rewriting anything it writes a full-fidelity copy of the session titled `<name> supercompact_copy_<date>_<time>`, so nothing is lost. The current turn is preserved untouched. A live Claude Code session holds the tail of its own transcript in memory and appends to it, so the entries it knows about have to keep existing — otherwise the next thing written points at a deleted entry and the history collapses on resume. ## Relaunching `--relaunch` hands off to `~/.claude-sessions-app/relaunch`, a script I own that knows how my terminal is arranged. Claude Sessions does not: it runs the script