wallacemartinss

Cc Cockpit — Development skill for Claude Code

Development community

Claude Code usage panel for GNOME: tray indicator with live rate-limit ring, local dashboard and terminal summary.

How to install Cc Cockpit

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

What Cc Cockpit does

Claude Code usage panel for GNOME: tray indicator with live rate-limit ring, local dashboard and terminal summary. Reads the official limits from the statusline payload — no credentials, no API calls.

Alternatives in Development

  • Oob — Out-of-band orchestrator — confirm BLIND SSRF/XXE/SQLi/RCE/Log4Shell by correlating interactsh callbacks to th 4.5k ★
  • Claude Swap — Switch between multiple Claude Code accounts, with automatic rate-limit rotation, usage dashboard, and paralle 2k ★
  • Nexting — Remote control for Claude Code, Codex, Grok, and Cursor on Mac or PC 1.3k ★

README

cc-cockpit

[![license: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE) [![PyPI](https://img.shields.io/pypi/v/cc-cockpit)](https://pypi.org/project/cc-cockpit/) [![AUR](https://img.shields.io/aur/version/cc-cockpit)](https://aur.archlinux.org/packages/cc-cockpit)

A Claude Code usage panel for GNOME: a tray indicator with a consumption ring, a local dashboard and a terminal summary.

Everything is read from what Claude Code already writes under `~/.claude`. It makes no network calls, reads no credentials and sends nothing anywhere.

The interface follows your OS language — English, Portuguese and Spanish are bundled — and can be pinned in the config file or with `--lang`.

What it shows

5h block how much the current rate-limit window has consumed, time to reset, hourly pace, projection to the end of the block, and how long until the reference ceiling. The window starts at the exact timestamp of its first request — not rounded to the hour — which is what makes the reset match what the CLI reports
7 days / today / month rolling totals, as a percentage of your own historical peak
Open sessions every live CLI instance: name, project, busy/idle, uptime, RAM, pid, and what that session has consumed
Projects ranked by consumption across the whole history
Blocks, days and hours time series showing when you actually spend
Token mix input / output / cache write 5m / cache write 1h / cache read, with the cache hit rate
Models, effort and subagents where the consumption really goes

Usage is measured in **API-equivalent USD**: what those messages would cost on the pay-as-you-go API. On a Pro/Max plan none of it is billed — the number works as a weight unit for consumption and shows how much the plan returns.

Install

**Debian / Ubuntu** — the `.deb` pulls in the GTK dependencies by itself:

# from the latest release
sudo apt install ./cc-cockpit_0.2.0_a