MoonshotAI / MoonshotAI/kimi-code

Feature request: display remaining token percentage / usage bar in editor footer

Open
#1,327 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

Problem

Currently there is no easy way to see, while working inside the editor, how much of the hourly token budget has been consumed and how much is left. When planning longer multi-step tasks (e.g., exploration → plan → implementation → verification) it is hard to guess whether enough tokens remain to finish the current session without hitting the rate/window limit.

Proposed feature

Add a token-usage indicator to the footer/status bar of the editor, for example:

  • A percentage label such as Tokens: 42% used or Tokens left: 58%.
  • Optionally a small progress bar that fills up as usage approaches the hourly limit.
  • Update it live (or after each turn) so it reflects the current time window.

Benefits

  • Developers can decide whether to keep iterating, start verification, or pause/split work before the hourly budget runs out.
  • Reduces surprise rate-limit errors in long sessions.
  • Helps calibrate prompt size and number of tool calls per turn.

Suggestions

  • Show both used and remaining tokens, e.g. 12.3M / 20M (61%).
  • Add a subtle warning color when usage crosses 80% or 90%.
  • If the limit is reset every hour, show the time remaining until the next reset.

Thank you for considering this!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the editor footer/status-bar entry point and the existing hourly token-budget accounting. Determine how current usage and reset timing are exposed to the editor, then define the display and warning behavior from the proposed examples. Done means the footer updates during a session and accurately shows used or remaining tokens, the limit, and reset timing where available.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.