mofchris

Claude Code Autopause — Productivity skill for Claude Code

Productivity community

Claude Code skill that pauses your session at a usage-limit percentage you pick, checkpoints the task, and resumes by itself when the limit resets.

How to install Claude Code Autopause

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

What Claude Code Autopause does

Claude Code skill that pauses your session at a usage-limit percentage you pick, checkpoints the task, and resumes by itself when the limit resets.

Alternatives in Productivity

  • Claudenightswatch — Autonomous task execution system for Claude CLI that monitors your usage windows and executes predefined tasks 352 ★
  • Cezar — Cezar is a parallel coding agents orchestrator 174 ★
  • Hybrid Auto — Generate PRD from task description and enter review mode 123 ★

README

claude-code-autopause

**Never lose work to the Claude usage limit again.**

A Claude Code skill that pauses your session at a percentage *you* pick, saves exactly where it was, and resumes by itself the moment the limit resets.

[![GitHub stars](https://img.shields.io/github/stars/mofchris/claude-code-autopause?style=flat&color=f0b429)](https://github.com/mofchris/claude-code-autopause/stargazers) [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![Node 18+](https://img.shields.io/badge/node-18%2B-3fb950.svg)](#requirements) [![Zero dependencies](https://img.shields.io/badge/dependencies-0-8b919e.svg)](scripts/usage-guard.mjs)

A Claude Code session hits 80% of the 5-hour window, pauses, writes a checkpoint, schedules a resume, and picks the task back up two hours later

The problem

You kick off a long task, walk away, and come back to a session that slammed into the 5-hour limit halfway through a refactor. Half the files are changed, tests never ran, and the model's working memory of what came next is gone. Or worse: you burned the whole weekly budget on Tuesday.

Usage monitors tell you the number. **This one acts on it.**

What it does

Pauses at your number 80% of the 5-hour window, 95% of the weekly window, whatever you choose. Per session if you want.
Blocks the expensive stuff only Build tools (Bash, Edit, Write, subagents) are denied by a hook. Reading, searching and planning still work.
Saves the exact spot A checkpoint file with the goal, what is done, the numbered next steps and how to verify. Nothing lives only in the model's head.
Resumes on its own Schedules a one-shot wake-up for reset time, re-checks usage, reads the checkpoint, carries on.
Warns before it bites As usage approaches the threshold the session is told to finish the current step cleanly, not sprint.
**Get