DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to watch context, cost and rate limits during a session with Claude Flightdeck

Keep the main panel open to see context fill, compactions, cost and rate-limit resets as you work.

Who it is forA developer running a long Claude Code session who needs to know how close the context window and plan limits are getting.

The problemContext, cost and rate-limit readings are scattered or hidden during a long session, so it is hard to tell when to compact, slow down or split the work.

The outcomeA docked pane beside the transcript showing model, effort, permission mode, the context gauge with compactions, cost, and the first two rate-limit windows with time to reset.

What you need first

  • Claude Code 2.1.287 or later
  • A terminal at least 144 columns wide for the pane to open on start, or any width with /flightdeck

Steps

  1. Inside Claude Code, run /plugin marketplace add scasella/claude-flightdeck
  2. Run /plugin install flightdeck@claude-flightdeck
  3. Run /reload-plugins
  4. Run /flightdeck to open the pane
  5. Read the main panel's context gauge and cost while you work; run /flightdeck reset to clear agents, checks, consults and log while keeping cost and rate limits

Prompt for your agent

In Claude Code 2.1.287 or later, install the scasella/claude-flightdeck plugin from its marketplace, run /reload-plugins and /flightdeck, then report the model, context percentage, compaction count and cost shown in the main panel. Verify the main panel appears before reporting.

Caveat. The cost and rate-limit figures show only when your plan reports them, and Flightdeck itself makes no network requests and calls no model.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page