← ClaudeAtlas

respawnlisted

Sets up automatic revival of this session after Claude's 5-hour usage limit is hit — waits until the window reopens, notifies the user, and resumes automatically unless the user cancels within a configurable grace window (default 5 min). Use when the user says "respawn", "set up respawn", "auto-resume", "revive this session", or wants to avoid having to remember to come back after a rate-limit cutoff. MUST be invoked proactively, BEFORE the account is actually blocked — does not work reactively after a cutoff. v0.2.0, field-tested through multiple overnight multi-window multi-session runs; not an officially supported Anthropic feature.
ruben-sj/respawn-skill · ★ 2 · AI & Automation · score 73
Install: claude install-skill ruben-sj/respawn-skill
# respawn Gaming metaphor: the session "dies" (gets blocked by the 5-hour usage limit), waits, and respawns automatically once the window reopens. **Critical precondition:** this must be set up BEFORE the account gets blocked. After a cutoff, no new message can be sent in any session until the window reopens — so there is no reactive way in. The user must invoke `/respawn` proactively (at the start of a heavy/long session, or when they notice they're approaching the limit). **Confirmed by repeated real-world use** (multiple overnight runs, multiple sessions running `/respawn` in parallel, multiple consecutive windows in a single run): a recurring `CronCreate` job does survive repeated rate-limit rejections and fires correctly once the window reopens, the detect → notify → cancel-window → resume flow works end to end (tested with the then-fixed 5-minute cancel window), and this holds across several concurrent sessions without interference. Still not an officially supported Anthropic feature — auto-resume after a rate limit is an open, unimplemented feature request (GitHub issues anthropics/claude-code #26775 and #36320) — but the core mechanism is no longer just a working assumption. **Known limitations** (tell the user this when the skill is activated, and again if they ask): - Requires this app/session to stay open for the entire waiting period. Believed (not independently confirmed) that `CronCreate` jobs are in-memory only ("session-only") and disappear without a trace