Installer replaces an existing statusLine.command, with no option to keep it

Author: CircleHPCreated Aug 28, 2026Updated Aug 28, 2026

Claude Code has a single statusLine.command, so installing ccstatusline 2.2.27 over another tool's takes it.

The flow does ask. With another command already configured, the install confirms with:

A status line is already configured: "<command>"
…
Replace it?

Yes is the only way forward — there's nothing that keeps what's there. Afterwards .statusLine holds ccstatusline's command and its own padding, with refreshInterval the only thing carried over from before.

That's destructive to whatever was registered. settings.json.orig is written first, so the old file is recoverable by hand, but nothing in the live configuration records what was replaced, and statusLine is read at session start — so the other tool goes quiet after the next restart with nothing to explain why.

I maintain Notchling, a Claude Code widget that has to register there too: rate_limits.* and context_window.* are handed to the status line and to nothing else, so there's no other way to read them. Installing ccstatusline over it stops it working.

Not asking for anything — just letting you know.