Schedule or reopen a specific Claude Code session after a rate-limit reset or other wait window. Use this skill when the user wants to resume a known Claude Code session by session ID, project path, or recent prompt, especially when a session is blocked by quota or rate limits and needs to come back at a specific time.
Use this skill to find a Claude Code session from local Claude history and schedule a detached relaunch after a reset time. The helper script reads ~/.claude/history.jsonl and ~/.claude/sessions/*.json, so it can resolve sessions by exact ID, recent prompt text, project path, or "latest".
Use the helper script at scripts/claude_session_resume.py.
Find likely sessions first when the user does not provide an exact session ID:
python scripts/claude_session_resume.py list --limit 10 --match "blog"
Schedule a detached reopen at an absolute local time:
python scripts/claude_session_resume.py schedule --session-id e8985fa4-5653-4233-bf1c-e1555bf3066d --at "2026-04-18 23:30"
Schedule a detached claude -c in the resolved project directory when the user explicitly wants "continue":
python scripts/claude_session_resume.py schedule --session-id e8985fa4-5653-4233-bf1c-e1555bf3066d --at "2026-04-18 04:01" --continue
Schedule it after a relative wait:
python scripts/claude_session_resume.py schedule --match "blog review" --in 90m
Use --fork only when the user wants a new branched session instead of reopening the original session.
list with --match using the project path, repo name, or a distinctive phrase from the last prompt.--in.schedule over running claude --resume directly from inside Claude Code. schedule spawns a background worker that survives after the current turn ends and opens a fresh terminal when the wait expires.--continue only when the user specifically wants claude -c or "continue the latest session in this directory".list shows recent sessions, last activity, project path, and the latest user prompt snippet.schedule accepts one session selector:
--session-id <uuid>--match <text>--latestschedule accepts one timing option:
--at "YYYY-MM-DD HH:MM"--in 90m--dry-run if the user wants to confirm the target before the launcher is started.--cwd <path> only when local metadata is missing or the user explicitly wants a different working directory.--continue to run claude -c in the resolved working directory instead of claude --resume <session-id>.--match is ambiguous, run list and show the candidates.--fork unless the user asks for a copy or branched continuation of the conversation.--continue as cwd-sensitive. If another Claude session becomes the most recent session in that directory before launch time, claude -c may reopen that one instead of the originally identified session.