v1.1.0 — The One That Counts Your Git Progress (Once You Ask It To)

Clepsydre — an always-on context-window status line for Claude Code.

This release teaches the branch segment to show how far along you are in git — ahead, behind, and uncommitted — but only once you ask it to. It also cleanly separates the maintainer experience from the user one, so the repo you install never nags you with work that isn't yours.

Highlights

• Git progress counts, opt-in — set CLEPSYDRE_GIT_COUNTS=1 once (globally or per-project) and the branch segment gains ↑2 ↓1 ±8: commits ahead of your upstream (to push), commits behind (to pull), and ± uncommitted changes. Each part shows only when it isn't zero. Off by default so the line stays instant — the branch alone is a cheap ref read, while the counts need a git status working-tree scan. Thanks @guillaumejay for the feature (#1)!
• Robust by design — if git ever hiccups with the counts on, the line falls back to the plain branch; the rest of the status line is never affected.
• A "How to read it" guide — the README now decodes a real status line piece by piece (branch + ↑↓±, the token gauge, and the memory segment).

Maintainer / user separation

• CLAUDE.md is now split: a lean, public-facing root (if you just installed Clepsydre, there is nothing to "resume" — git pull to update) plus a maintainers/CLAUDE.md that only kicks in when a maintainer explicitly asks to develop. No more "continue the plan?" prompts for people who just want to use the status line.

Turn on the git counts

Add this to the "env" block of your settings.json (global ~/.claude/settings.json or a project's .claude/settings.json):

{ "env": { "CLEPSYDRE_GIT_COUNTS": "1" } }

Install / update

Already installed? Just git pull — no re-install. New here:

git clone git@github.com:tpierrain/clepsydre.git ~/clepsydre
cd ~/clepsydre && node install.mjs

Then restart Claude Code.

⚠️ Ignore the "Source code (zip / tar.gz)" archives below. GitHub attaches them automatically and they're useless for Clepsydre: the installer points your status line at an absolute path inside your clone, so updates land with a plain git pull — a downloaded archive has no git history to pull.