MoonshotAI / MoonshotAI/kimi-cli
Feature request: non-interactive `kimi usage` (or `/usage` via --print) for programmatic quota checks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.4k
- Forks
- 1.3k
- Avg merge
- 9h 47m
- Merged PRs (30d)
- 2
Description
Problem
The only way to inspect remaining Kimi Code quota is via the interactive `/usage` slash command inside the REPL. There's no way to read it from a script, CI step, dashboard, or menu-bar widget.
```bash
$ kimi -p "/usage" --print
• Unknown slash command "/usage".
```
In `-p` / `--print` mode slash commands are rejected, so the only path is spawning the full TUI and screen-scraping the rendered box. That's fragile because Kimi's TUI emits:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the REPL /usage slash command and how kimi -p/--print rejects slash commands. Compare the interactive quota output with the requested programmatic entry point; done means a script can retrieve remaining quota without starting the TUI or screen-scraping it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100