pqant

Claude Continuity — Development skill for Claude Code

Development community

Zero-touch session rotation and supervision for Claude Code.

How to install Claude Continuity

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

What Claude Continuity does

Zero-touch session rotation and supervision for Claude Code.

Alternatives in Development

  • Ccusage — CLI for analyzing Claude Code/Codex usage from local JSONL files 11.8k ★
  • Claude Swap — Switch between multiple Claude Code accounts, with automatic rate-limit rotation, usage dashboard, and paralle 2k ★
  • Ccnexus — A smart API endpoint rotation proxy for Claude Code 786 ★

README

cc-continuity

Zero-touch session rotation and supervision for Claude Code.

**Why it exists.** Long sessions die when the context window fills up — and local LLMs make it worse: their window is fixed and small, and the built-in compaction (`/compact`, auto-compact) is a lossy one-shot summary. With a small model it silently drops decisions, rejected approaches and the exact stopping point, and every compaction then summarizes a summary, so the drift compounds. cc-continuity exists to give long work room to breathe inside the window: at a safe threshold it rotates the session with a structured, validated handoff instead of a lossy summary.

The goal is to let an agent drive a planned project end-to-end, from 0 to done, with a human involved only when the agent is truly blocked. This repository is the proof of concept: it was developed with cc-continuity itself, and the full development history is in this git log.

cc-continuity watches the context ratio and, when it crosses a threshold, rotates the session with no user action:

  1. the agent finishes the current step,
  2. cc-continuity makes it write a validated handoff,
  3. the git tree is snapshotted non-invasively (refs/continuity/* refs — no commits, no tags, no branches touched),
  4. the context is cleared and the session renamed,
  5. a continuation prompt is injected and the successor session starts with Continuing from cp- (-).

An optional launchd **watchdog** keeps long unattended runs recoverable when the model server (for example a local vLLM box) dies or freezes, and optional **ntfy** pushes let you watch from your phone.

How it works

The whole flow in one picture — the automatic session loop, the optional watchdog, and the opt-in notifications:

![cc-continuity flow: session loop, watchdog, notifications](docs/diagrams/flow.en.png)

Requirements

  • macOS (v1 — Linux/systemd is a documented seam, not yet implemented)
  • Python ≥ 3.11 (standard library only at runtime)
  • tm