Skip to main content

quota

❖ Communityv2.10.0★ 88

Desktop · by rarf · added Sep 19, 2026 · updated Oct 9, 2026

Per-provider quota / rate-limit status via /quota command and desktop widget. Reads precomputed quota_cache.json so the widget never does network I/O.

Disclosure — refreshes your Gemini OAuth token using the Gemini CLI's public client identity, in memory only; queries Copilot's internal usage endpoint with VS Code client headers and Anthropic's OAuth usage endpoint using the hermes-quota-plugin User-Agent; optional additional Claude accounts read access tokens only from explicitly configured Claude Code credentials files and send them only to Anthropic's fixed OAuth usage endpoint (read-only, no refresh-token exchange or credential write-back; tokens and paths excluded from the quota cache). Linux extra accounts verified; Windows experimental, extra macOS Keychain accounts unsupported. The openai-codex check reads every saved Codex account from Hermes' own auth.json credential pool (read-only, never refreshed; expired accounts show reauth-required) and queries the Codex usage endpoint with the codex-cli User-Agent; the opencode-go check reads the OpenCode CLI's local auth.json, Hermes' auth.json pool and OPENCODE_GO_API_KEY_N variables (read-only). The cursor check reads the Cursor CLI token from the macOS Keychain or Cursor's auth.json (read-only, never refreshed or rewritten; on expiry it asks you to run cursor-agent login) and queries api2.cursor.sh; the opt-in (default off) antigravity check reads Antigravity's OAuth token from Windows Credential Manager, the macOS Keychain or ~/.gemini/antigravity-cli (read-only), refreshes it in memory with Antigravity's public client identity and sends Antigravity's User-Agent to Google's cloudcode endpoint; the opt-in (default off) grok.com check reads local browser cookies, using secret-tool on Linux or the macOS Keychain for the browser's Safe Storage key and decrypting only grok.com cookies from a temporary copy of the cookie DB; the commandcode check reads ~/.commandcode/auth.json (read-only) or Hermes' credential store and uses the Command Code CLI's User-Agent; zai, kimi, minimax, deepseek, openrouter, ollama (which may read OLLAMA_API_KEY from ~/.hermes/.env and calls ollama.com/api/usage and /api/me) and experientiallabs send keys from Hermes' credential store or env only to their own vendor's usage or balance endpoints.

Open in Hermes Desktop

hermes plugins install quota

Repository ↗Reviewed source @ ce8593a ↗Documentation ↗

Screenshots

quota screenshot 1

quota screenshot 2

What it adds

Hooks 2

footerusage_extra

README

From the reviewed commit ce8593a ↗; it updates when the author re-pins.

Hermes Quota

Quota in Hermes Desktop

See provider quotas, reset times and account balances in Hermes Desktop and the CLI—without adding network calls to every UI render.

What you get

A docked pane and status-bar indicator with per-provider usage.
Model-specific quota windows and reset times when the vendor supplies them.
Separate, configurable Claude account cards; no summed or invented allowances.
Honest unavailable states and opt-in access to sensitive credential sources.

Install

git clone https://github.com/rarf/hermes-quota-plugin.git
cd hermes-quota-plugin
./install.sh

The source installer enables quota for all existing profiles. Review that scope before running it. For remote Desktop setups, install/update the widget on the computer running the app as well as the backend on the gateway. Installation and updates.

hermes plugins doctor quota --ci
hermes quota refresh
hermes quota status

Multiple Claude accounts

Additional accounts are explicitly configured by directory and display label. Labels such as Work, Personal or Account 2 are user-configurable—not hardcoded. Linux is verified; additional platform limitations are documented.

Configure Claude accounts →

Privacy and security

Extra Claude accounts are opt-in and read-only: no refresh-token exchange, credential write-back or tokens in the display cache. Requests identify this plugin rather than Claude Code. Primary-account resolution remains Hermes-core behavior. Other providers may use opt-in browser/OS credential-store reads and vendor client identities; see provider disclosures. Python plugins are trusted host code, not sandboxed applications. Third-party login reads require disclosure and maintainer judgment for catalog admission. Security details and limitations.

Documentation

MIT · License

More by rarf

All 2 plugins by rarf →

optmem-hermes❖ Community★ 17

Independent Hermes integration of Victor Taelin's OptMem design: local, append-only memory with regex/BM25 recall and a bounded wake digest. Hybrid and guarded OptMem-only modes; verified migration and rollback. Local by default. Compaction is manual unless auto_nap is enabled. Optional LLM summaries run only when both auto_nap and llm_summary are on; they send memory blocks to the configured provider via host-owned authentication and may incur token costs. Summaries are lossy, raw records remain recoverable, and conflicts are not resolved automatically. Wake consumes model context. See README for upstream attribution. Disclosure — memory is stored locally under HERMES_HOME; optional auto_nap+llm_summary sends stored memory lines to the user's configured model provider; the optmem-only mode (explicit CLI with --yes) disables Hermes' built-in MEMORY.md/USER.md injection after a verified backup.

← Back to the catalog · catalog built Oct 16, 2026