Stop paying for wasted tokens. See exactly where your AI spend goes — and automatically cut what you don't need.
Explore the docs »
Download
·
Report Bug
·
Request Feature
Table of Contents
Veyr is a native macOS menu bar app that reads your local Claude Code session logs — no proxy, no account, no traffic interception. It shows real-time spend by project, enforces budgets, and tells your coding agent how to be more efficient, automatically.
~/.claude/projects/**/*.jsonl (logs Claude Code already writes)
│
▼
Veyr.app (menu bar)
│
├──▶ spend by project · budgets · 13-rule optimization engine
├──▶ ~/.veyr/agent-status/VEYR_STATUS.json (agents read this)
└──▶ CLAUDE.md spend + graph block (Claude Code reads this)
Here's why Veyr exists:
- LLM costs are invisible until the bill arrives — Veyr makes them visible in real time
- Your coding agent doesn't know it's being wasteful — Veyr tells it, automatically, every session
- You shouldn't need a proxy or a cloud account to see where your money goes
Built on CodexBar by Peter Steinberger (MIT) · codebase graph powered by Graphify (YC S26) · see CREDITS.md.
— native macOS menu bar app
— CLI, VS Code extension
— ML classifier training (dev-side), Graphify
packages/dashboard (React) is a legacy piece still in this repo, left untouched from an earlier iteration of Veyr — not part of the current three-surface product; see Repository Layout. The old proxy server and Electron app have already been fully extracted onto a separate branch.
- macOS 14+ (Sonoma) for the native Mac app
- Node.js 20+ for the CLI and VS Code extension
- Python 3.8+ is optional — installed automatically on first launch for codebase graph features (see Automatic Dependency Installation)
- Xcode 16+ only if building from source
No account, no proxy, no configuration needed to get started.
-
Download
Veyr-0.2.1.dmgfrom the Veyr download page -
Install — open the DMG, drag Veyr to Applications, open it
-
Bypass Gatekeeper (required — builds are not yet notarized):
xattr -cr /Applications/Veyr.app
This removes the quarantine flag so macOS allows the app to run. It only affects Veyr.
-
Start a Claude Code session — Veyr detects it automatically. The menu bar shows today's spend with a pulsing dot while a session is active.
-
(Optional) Enable CLAUDE.md injection — on by default. Veyr keeps a marker-delimited spend and graph block in your active project's
CLAUDE.mdso Claude Code sees its burn rate, budget status, and optimization recommendations at every session start. Toggle it off in Settings → Veyr. -
(Optional) AI task classification — add your Anthropic API key in Settings → Veyr (stored in the macOS Keychain). Veyr then classifies each agent turn as simple/moderate/complex using Haiku (~$0.01/day typical) and surfaces what you're wasting by running simple tasks on frontier models.
Build from source (requires Swift 6 CLT + Xcode 16+):
cd packages/desktop-mac
./Scripts/package_app.sh release && open Veyr.app-
Download
veyr-vscode-0.2.1.vsixfrom the Veyr download page -
Open VS Code → Extensions panel (
Cmd+Shift+X) →···→ Install from VSIX… → select the file -
The extension activates automatically. You'll see live session cost in the status bar:
$(graph-line) $0.84 · 14k↓ 3k↑ · 23% saved ⚡The Veyr sidebar panel shows burn rate, cache hit rate, codebase graph status, and one-click optimization commands.
Note: The Mac app must be running — it writes the agent feed the VS Code extension reads.
brew install --cask hethb/veyr/veyr # macOS app
brew install hethb/veyr/veyr # CLI| Feature | Description |
|---|---|
| Menu bar spend | Today's cost at a glance, pulsing dot during active sessions. Spend window shows 7-day chart, per-project breakdown, and session timeline. |
| Agent feed | ~/.veyr/agent-status/VEYR_STATUS.json rewritten every 30s: session cost, burn rate, cache hit rate, budgets, and agent_instructions any coding agent can act on. |
| CLAUDE.md injection | Spend status and codebase graph summary injected into your project's CLAUDE.md so Claude Code reads them automatically every session. |
| Codebase graph | Graphify-powered knowledge graph of your codebase — call graph, dependency chain, critical path, test coverage gaps. Saves 60–90% of exploration tokens per session. |
| 13-rule optimization engine | Wrong model, poor cache usage, runaway sessions, retry loops, tool-list bloat, redundant reads, and more — each with an estimated monthly saving. |
| Budgets | Per-project monthly caps with macOS notifications at 80% and 100%. Agents see budget status in their feed and adjust behavior accordingly. |
| AI task classification | Optional, uses your API key. Haiku classifies every agent turn — Veyr reports the cost wasted running simple tasks on expensive frontier models. |
| Prompt caching awareness | Detects cache-eligible prompts in your session history and flags low cache-hit-rate features as a suggestion. Enabling native provider caching is a call your coding agent can act on — Veyr doesn't inject anything in the request path. |
| Document → Markdown | Converts PDFs, Word docs, HTML, CSV, JSON, XML into compact LLM-friendly Markdown. 70–90% fewer input tokens than raw files. |
| VS Code extension | Live session cost in status bar, sidebar panel with burn rate and suggestions, one-click model switch commands. |
| Browser extension (legacy, optional) | Chrome MV3 overlay for chatgpt.com and claude.ai — live token counts, complexity-aware prompt compression. Not one of Veyr's core three surfaces; see Repository Layout. |
| Terminal CLI | veyr dashboard, veyr status, veyr usage, veyr graph, veyr rules, veyr savings — full parity with the Mac app and VS Code surfaces, reading the same local data. |
Veyr analyzes your session history and surfaces specific, actionable ways to cut token spend. All analysis runs in-process over local data — no external API or LLM calls.
Each suggestion includes an estimated monthly saving, the evidence that triggered it, and a concrete action. The highest-impact suggestion is flagged as a quick win.
| # | Rule | What it detects | Action |
|---|---|---|---|
| 1 | Wrong model | Feature averages <500 prompt tokens but uses frontier model, costs >$5/mo | Route to mini/Haiku (~80% cheaper) |
| 2 | Ballooning completions | Responses >2x input length, 20+ calls, >$3/mo | Cap max_tokens |
| 3 | Errors burning tokens | >10% error rate on 10+ calls in 7 days | Fix the underlying error |
| 4 | One feature dominates | Single feature >60% of total spend | Add budget cap or model override |
| 5 | Redundant long template | Same prompt hash 50+ times/mo averaging >800 tokens | Compress the template |
| 6 | Low cache hit rate | Feature averages ≥1024 tokens, 20+ calls, >$2/mo, <20% cache reads | Enable prompt caching |
| G1 | Leaf node on expensive model | Active function has ≤2 connections but runs on Opus/GPT-4o | Switch to Haiku |
| G2 | God node warning | Active function has >20 connections | Review blast radius before editing |
| G3 | Unexplored dependencies | Active file imports never-explored files | Check graph summary first |
| G4 | Redundant file reads | Agent re-reads stable files every session | Use graph summary instead |
| G5 | Test coverage gap | High-connectivity function with no tests, >$5/mo spend | Write a test first |
| 11 | Long outputs on simple tasks | Average output >1500 tokens, majority simple tasks | Add output constraints |
| 12 | Verbose JSON examples | System prompt contains example response blocks | Use structured outputs instead |
| 13 | Batch API candidates | Non-streaming background jobs | Use OpenAI Batch API (50% cheaper) |
Suggestions appear after at least 7 days of traffic. Graph-powered rules (G1–G5) require Python 3.8+ for the codebase graph.
Chrome MV3 overlay for chatgpt.com and claude.ai: a floating widget with live token counts, estimated cost, and rule-based prompt tips as you type. This is a standalone add-on from an earlier iteration of Veyr, not one of the three core surfaces, and it ran entirely local-estimate — it did not require or talk to any Veyr backend.
Its source has already been extracted out of this repo (see Repository Layout); only a packaged build artifact remains at packages/browser-extension/dist-zip/veyr-extension.zip. To load it: unzip that file, then chrome://extensions → Developer mode → Load unpacked → the unzipped folder.
npm install -g getcanopy # or: brew install hethb/veyr/veyr
npm install -g getcanopy@latest # update — the CLI nudges you with this command when a newer version is out
veyr # terminal dashboard: session, usage, graph, savings, rules + all commands
veyr status # current session cost, budget, alerts, tool health, recommendations
veyr usage # per-agent / per-project spend, today/week/month, session timeline
veyr graph # Graphify graph status + what Veyr understands about the project
veyr rules # view/toggle the CLAUDE.md agent-guidance rule set
veyr savings # confidence-tagged savings, lifetime + per projectThe dashboard renders once automatically on first run as a welcome screen — no account, no key, no setup. See packages/cli/README.md for the full command table.
The Veyr VS Code panel shows live spend and optimization suggestions for the active Claude Code session, read from the same local agent feed the menu bar app writes — no proxy, no ANTHROPIC_BASE_URL change.
packages/desktop-mac reads coding-agent logs directly from disk — Claude Code's ~/.claude/projects/**/*.jsonl, Codex CLI sessions, and 50+ other providers — no proxy required.
cd packages/desktop-mac
make startRequires macOS 14+ and Xcode 16+.
Helicone shows you that you're spending money. Veyr tells you which feature is responsible and how to spend less.
| Helicone | Veyr | |
|---|---|---|
| Per-request logging | ✓ (proxy) | ✓ (reads local session logs, no proxy) |
| Spend UI | ✓ hosted dashboard | ✓ menu bar app + VS Code panel, local |
| Works without a proxy or account | ✘ | ✓ |
| Cost by project/feature | ⚠ manual tags | ✓ auto-inferred |
| 13-rule optimization engine | ✘ | ✓ |
| Codebase graph (Graphify) | ✘ | ✓ |
| Agent-readable feed | ✘ | ✓ (agents self-optimize) |
| CLAUDE.md auto-injection | ✘ | ✓ |
The three core surfaces, plus one legacy package still physically in this repo:
veyr/
├── packages/
│ ├── desktop-mac/ # core: native Swift menu bar app (built on CodexBar)
│ ├── desktop-windows/ # in progress: native Windows tray app (forked from Win-CodexBar)
│ ├── vscode-extension/ # core: live session cost + optimization suggestions in VS Code
│ ├── cli/ # core: veyr terminal CLI (status, suggestions)
│ ├── dashboard/ # legacy: React dashboard UI for the old proxy-based product — not part of the current product, untouched
│ ├── browser-extension/ # legacy remnant: only a packaged build artifact (dist-zip/), no source
│ └── ml/ # dev-side Python: classifier training on local session data
├── examples/ # legacy: old proxy integration demo (customer-demo.mjs), untouched
├── CREDITS.md # open source attribution
├── package.json # workspace root
└── .env.example
The proxy server and the SDK wrapper (canopy-sdk) it shipped with, plus the legacy Electron desktop app, have already been fully extracted out of this repo — they're archived on the archive/promptlens-gateway branch, not on main. packages/dashboard is the one legacy piece still physically here: it's a frontend for that now-archived proxy and has no backend to talk to on main. It's left untouched and unused by the three core surfaces.
To develop the current product, see Download & Get Started for building the macOS app from source; packages/vscode-extension and packages/cli build with standard npm install + their own npm run build.
- Node.js 20+
git clone https://github.com/hethb/Veyr.git
cd Veyr
npm install
packages/dashboardis a legacy frontend left untouched from an earlier proxy-based iteration of Veyr (see Repository Layout). Its backend — the proxy — has already been extracted out of this repo onto thearchive/promptlens-gatewaybranch, sonpm run dev:dashboardwill start the UI but it has nothing to talk to onmain. It isn't part of, or required by, the three core surfaces.
Veyr automatically installs Graphify (a Python package by Graphify Labs, YC S26) on first launch if Python 3.10+ is available on your system. The install is silent and pinned to an exact, Veyr-audited commit — never "latest", and never by bare package name:
python3 -m pip install --quiet --user \
"https://github.com/Graphify-Labs/graphify/archive/<pinned-commit>.tar.gz"Why pinned? The graphify name on PyPI is currently unclaimed (upstream temporarily publishes as graphifyy), and a silent installer must not resolve mutable names. Each Veyr release bumps the pin deliberately — the current commit is defined in GraphifyPin.
No elevated permissions (no sudo) are required. If your Python is externally managed (Homebrew/PEP 668) and refuses --user installs, Veyr falls back to a private venv at ~/.veyr/graphify-venv — your own Python environments are never touched. If you already have Graphify installed, Veyr uses your copy and installs nothing.
Veyr only ever runs Graphify's pure-AST mode (graphify update) — tree-sitter parsing on your machine, zero LLM calls, no code sent externally.
To manage it yourself:
pip3 install graphifyy # install manually (upstream's current PyPI name)
pip3 uninstall graphifyy # remove it
rm -rf ~/.veyr/graphify-venv # remove Veyr's fallback venv, if createdDisable the feature entirely with "codebaseGraph": false in ~/.veyr/config.json.
- The Mac app reads your local Claude Code and Codex log files from disk. Nothing leaves your machine by default.
- Session history is stored in
~/.veyr/locally. - The optional AI classifier calls Anthropic's API using your key, only when you add one in Settings.
- All ML training data stays in
~/.veyr/ml/— never uploaded. - Graphify analyzes your codebase on-device (pure AST parsing, no LLM calls) — no source code leaves your machine. Veyr installs it automatically on first launch, pinned to an audited commit; see Automatic Dependency Installation.
Why each permission is requested, and how to control it.
- Full Disk Access (optional) — only required to read Safari cookies/local storage for web-based providers. If you don't grant it, use another supported browser, manual cookies/API keys, OAuth, or CLI/local sources where that provider supports them.
- Keychain access (prompted by macOS):
- Chromium cookie import needs the browser's "Safe Storage" key to decrypt cookies.
- Claude OAuth bootstrap may read the Claude CLI Keychain item when Veyr has no usable cached credentials.
- Veyr may use Keychain for browser cookie decryption, cached cookie headers, and OAuth/device-flow credentials where those sources require it.
- Files & Folders prompts (folder/volume access) — Veyr launches provider CLIs and local probes for some providers. If those helpers read a project directory or external drive, macOS may ask Veyr for that folder/volume (e.g., Desktop or an external volume). This is driven by the helper's working directory, not background disk scanning.
- What we do not request in the background — no Screen Recording or Accessibility permissions. User-triggered helper actions may ask macOS for Automation permission to open Terminal. No passwords are stored (browser cookies are reused only when you opt in).
- Open Keychain Access.app → login keychain → search for the prompted item (for Claude OAuth, usually "Claude Code-credentials").
- Open the item → Access Control → add
Veyr.appunder "Always allow access by these applications". - Prefer adding just Veyr (avoid "Allow all applications" unless you want it wide open).
- Relaunch Veyr after saving.
Do the same for a browser's cookie storage: find its "Safe Storage" key (e.g., "Chrome Safe Storage", "Brave Safe Storage", "Microsoft Edge Safe Storage"), open it, add Veyr.app under Access Control. That removes the prompt when Veyr decrypts cookies for that browser.
Last resort — stop all Keychain reads entirely: if "Always Allow" doesn't stick (e.g., macOS resets the ACL after a Chromium update or a partition_id reset), open Veyr → Settings → Advanced → Keychain access and enable Disable Keychain access. Veyr will no longer touch the Keychain. Browser-cookie-based providers will be skipped, but Claude/Codex OAuth via the CLI still works (it reads ~/.codex / ~/.claude config files, not the Keychain).
Still getting prompted after uninstalling? Deleting the app prevents a new launch from that bundle, but an already-running Veyr process can keep requesting Keychain access until it quits. Check for that process, a Login Item, another installed copy, or a prompt that names a different requesting binary/path before assuming something is wrong.
- Native macOS menu bar app (CodexBar foundation)
- Real-time spend by project and session
- 13-rule optimization suggestion engine
- Per-project budget caps and macOS notifications
- Agent-readable feed (VEYR_STATUS.json)
- CLAUDE.md auto-injection
- VS Code extension with live cost display
- Browser extension (ChatGPT & Claude.ai)
- Terminal CLI
- Prompt caching detection (low cache-hit-rate suggestions)
- Document → Markdown converter
- AI task complexity classifier
- Graphify codebase graph integration (graph-aware suggestions, CLAUDE.md + VEYR_STATUS.json context)
- Interactive graph visualization in the menu bar app
- Homebrew distribution (formula + cask)
- Apple notarization (Gatekeeper-clean DMG)
- JetBrains IDE extension
- Windows and Linux support
See the open issues for proposed features and known bugs.
Contributions are what make open source such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would improve Veyr, please fork the repo and create a pull request. You can also open an issue with the tag enhancement.
- Fork the project
- Create your feature branch
git checkout -b feature/AmazingFeature
- Commit your changes
git commit -m 'Add some AmazingFeature' - Push to the branch
git push origin feature/AmazingFeature
- Open a Pull Request
Distributed under the MIT License. See LICENSE for more information.
Heth Bhatt — xlnc.hethbhatt@gmail.com
Project Link: https://github.com/hethb/Veyr
- CodexBar by Peter Steinberger (@steipete) — the foundation for Veyr's native Mac app. MIT licensed.
- Graphify by Graphify Labs (YC S26) — AST-based codebase knowledge graphs powering Veyr's structural optimization.
- Choose an Open Source License
- Img Shields
- Best README Template