Beezi plugin for Claude Code
Claude Code plugin tracking the cost of AI work: tokens and tool calls per Beezi task and a spend summary in the terminal.
- 63 ★ on the repository
- Last commit
Extended access
Why this level
- The plugin sends usage, account and machine data to the Beezi server.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/beezi-plugin-for-claude-codeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin sends usage, account and machine data to the Beezi server.
This is third-party code. Review the repository files before installing.
What it does
The Beezi plugin hooks into Claude Code session lifecycle and sends analytics to Beezi: how many tokens were spent, how many tool calls were made and which task branch the work ran on. After signing in with `/beezi:login`, work on Beezi task branches is tracked automatically and nothing else needs to run. `/beezi:analytics` gives a personal summary for 7 or 30 days: spend, sessions, top model, alert status and up to three recommendations. `/beezi:settings`, `/beezi:sync` and `/beezi:logout` change sending rules per folder and repository, upload past sessions and revoke the machine's access. The sign-in token sits in the OS secret store.
Who it is for. Teams on Beezi who want the cost of AI development per task, and developers tracking their own spend.
Good fit when
- You need to see how many tokens and how much money one Beezi task cost.
- A developer wants this week's spend right in the terminal.
- Past Claude Code sessions need uploading to Beezi.
- Analytics must not be sent from some folders and rules are set per repository.
- A machine's access is revoked after changing laptops.
Not a fit when
- There is no Beezi account, and the plugin works only with one.
- Account and machine data must not go to a third party.
- Spend analytics independent of Beezi is needed.
Example request
Show my Claude Code spend over the last 30 days: sessions, top model and recommendations.Limitations
The plugin works only with a Beezi account and sends nothing before `/beezi:login`. It transmits spend numbers, the session name, the `origin` address without credentials, the machine name, the Claude account id and email, subscription type and fingerprints of environment keys, and hourly the list of enabled plugins. Prompt text, replies, code and file paths are not sent. Diagnostic telemetry is switched on separately. After upgrading to 0.29.0 restart Claude Code once.
How to disable. Run `/beezi:logout`: the machine is unlinked, access is revoked and credentials are removed. Then disable the plugin in the plugin manager. Local state sits in `~/.beezi`.
FAQ
What does the plugin never send?
Prompt and reply text, file contents, code, diffs, paths, tool inputs and outputs, sign-in tokens and API keys.
How to upload past sessions?
With `/beezi:sync`, which uploads Claude Code sessions Beezi does not have yet. History is also uploaded once at the end of `/beezi:login`.
What is in the `/beezi:analytics` summary?
Spend, sessions, top model, alert status and up to three recommendations. The default window is 7 days and `30d` widens it.
How to skip some folders?
In `/beezi:settings` set a rule per repository or folder, including a do-not-track mode, and a default for new ones.
Can the API address be changed?
Yes, `BEEZI_API_URL` and `BEEZI_MCP_URL` set the addresses and `BEEZI_HOME` moves local state.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin: a status line with context, 5-hour and 7-day limits, cost and usage of Codex, Gemini and z.ai
claudetop shows session cost, cache hit rate, plan limit windows and overspend alerts in the Claude Code status line
Token and cost reports for Claude Code, Codex, Gemini CLI and other agents from local logs, by day, month and session
CLI that counts token usage of Claude Code, Codex, Cursor and other agents from local logs and syncs it to vibecafe.ai.
Counts token use and cost of Claude Code and Codex sessions from local logs and shows remaining limits in the status line
A CLI and MCP server that tally token spend across 41 tools and agents, break it down by project and model, and help cut wasted tokens
README in short
The plugin gathers per-task spend analysis and sends it to Beezi. What is sent and where sign-in is stored are listed in the plugin README.