You don’t always lose sessions to rate limits — you lose them to context switches. Power Claude’s Resume Stalled workflow inventories unfinished agent sessions and continues them deliberately (often in isolated worktrees), instead of hoping you remember which tab died last Tuesday.
TL;DR
| Tool | Best for |
|---|---|
| Auto-Resume / Rewake | Same session, temporary stop, still “the” live job |
| Resume Stalled | Many abandoned sessions across time; finish the backlog |
| Cross-model hang scan | Sessions parked under another vendor client |
When to use Resume Stalled
- You have a graveyard of half-done agent threads.
- Auto-resume would be wrong (old context, wrong branch, wrong machine).
- You want worktree isolation so finishing one doesn’t trash another.
- You’re doing fleet / compliance sweeps across repos.
How to run
- Command Palette → Power Claude: Finish Stalled Sessions (
powerClaude.resumeStalledSessions). - Review the inventory (age, path, status).
- Confirm which sessions to continue.
- Prefer session worktrees for code edits; land to local main via harness tools when done.
- Optional: Cross-Model Hanging Sessions for Claude↔other-client leftovers.
Safety
- Don’t auto-resume unknown ancient sessions with destructive tool rights.
- Prefer read-only inventory first.
- Kill switch still applies for automated continuation.
- Never
git pushfrom agents unless your process explicitly allows it (Power Claude harness defaults: local land only).
FAQ
Is this the same as Auto-Rewake?
No. Rewake continues a live continuity policy. Resume Stalled is backlog completion.
Related
Primary sources
- Commands:
powerClaude.resumeStalledSessions,powerClaude.crossModelSessions - Feature doc:
docs/features/resume-stalled/ - Harness skill: resume-stalled
Independent third-party software by Neural-LLM. Not affiliated with Anthropic.