Skip to content

Run ccstatusline from a mise install instead of npx - #66

Merged
technicalpickles merged 1 commit into
mainfrom
ccstatusline-direct-install
Oct 16, 2026
Merged

technicalpickles merged 1 commit into
mainfrom
ccstatusline-direct-install

Conversation

@technicalpickles

Copy link
Copy Markdown
Owner

Summary

  • The statusline now runs ccstatusline from a mise install (npm:ccstatusline, still pinned at 2.2.32) instead of npx -y ccstatusline@2.2.32.
  • Pinning in Pin ccstatusline to 2.2.32 #58 skipped the registry lookup, but npm's own startup still cost 21-68% CPU on every statusline refresh, in every session. Calling the binary directly cuts that to roughly a third of the CPU and half the wall time per run.

Rollout

Order matters on each machine: pull, mise install, then ./claudeconfig.sh. If claudeconfig.sh goes first, the statusline shows "command not found" until mise installs it.

Test plan

  • After the steps above, command -v ccstatusline resolves to the mise shim, and the statusline renders in a new Claude session.

🤖 Generated with Claude Code

Pinning to 2.2.32 (#58) skipped the registry lookup but not npm's own
startup, which still sampled at 21-68% CPU per statusline refresh in
every session. Install it via mise npm:ccstatusline at the same pin and
call the binary directly. Locally: ~2x faster wall time and ~3x less
CPU per invocation (hyperfine, 10 runs).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@technicalpickles
technicalpickles merged commit 81f935b into main Oct 16, 2026
1 check passed
@technicalpickles
technicalpickles deleted the ccstatusline-direct-install branch October 16, 2026 17:47
technicalpickles added a commit that referenced this pull request Oct 16, 2026
Covers the pin, the mise install + shim (#66), and the HEAD/index-keyed
git cache, with the per-refresh breakdown and the Rust statusline
benchmarks that were considered.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant