Agent Optics

See every limit before it sees you.

Agent Optics shows, live, how much of each AI coding agent's quota you have used and how much is left, across every account you own. It sits in the sidebar of VS Code, Antigravity, Cursor and Windsurf, refreshes every 2 minutes, and tells you which account to use next.

What it tracks

Add as many accounts per agent as you like. A guided sheet walks you through connecting each one, step by step, with a toggle for your first account and for adding another: how to sign in with the agent's own login, connect it here, share skills, plugins, MCP servers and sessions between the accounts, and switch between them.

Features

• Live meters for every limit, with a hairline showing where even spending would be, so you can tell at a glance if you are ahead of pace.
• Detail on demand: expand a card for exact numbers, burn rate, when you will run out, and where the usage went.
• Dashboard with history charts (24 hours, 7 days, 30 days), the account with the most room right now, and advice such as "Switch to your other account" or "34% of your weekly quota expires unused tomorrow".
• Status bar meter: pin an agent and it shows whichever of its accounts is current, or leave it unpinned to show the account nearest its limit.
• Alerts at 75%, 85% and 95%, and before quota expires unused.
• Switch accounts for Claude Code and Codex: every account shows Current or Use, in the panel and the dashboard. A switch waits until no session of that agent is running, so work in progress never changes account. Shared accounts of one agent use the same skills, plugins, MCP servers, sessions and the agents list (resume any of them from any account), memory and prompt history; only the login differs.
• Share accounts in one click for Claude Code, Gemini CLI and Kimi Code: a newly connected account asks once whether to link to your main account or keep its own data, and you can choose what to share (chats, tools, settings, prompt history). Folders are linked and settings files symlinked, links that break repair themselves, and the dashboard's Accounts card and a small status bar icon show any account that is not linked yet, with the fix.
• Stop all sessions for Claude Code, Codex, Gemini CLI, Kimi Code and Cursor Agent, after a confirm that names each program it will end.

What you set up yourself, per agent

On Windows, linking single files such as settings.json needs Developer Mode, but only while the link is made; Agent Optics says when you can turn it off again. Without it, folders still link and settings are copied.

Set up a shared second Claude account by hand

The Another account guide in Agent Optics walks you through this, and Agent Optics shares the folders as soon as you connect the new account. To set it up without the extension, paste this prompt into Claude Code:

Set up a second Claude Code account on this machine that shares everything with my current one except the login. Follow these rules exactly and stop to ask me if anything does not match.

1. My shared home is ~/.claude. If the CLAUDE_CONFIG_DIR environment variable is set, tell me its value and stop.
2. Create the folder ~/.claude-accounts/work (use another name only if I give one). If it already exists, stop and ask me.
3. Inside the new folder, create a link to each of these folders in ~/.claude, creating the folder in ~/.claude first if it is missing: agents, commands, skills, plugins, local-marketplace, output-styles, rules, projects, tasks, session-env, paste-cache, plans, todos, file-history, jobs, sessions. On Windows use directory junctions (mklink /J), elsewhere symbolic links (ln -s). Do not link ide, daemon or shell-snapshots; they belong to one running Claude.
4. Symlink settings.json, CLAUDE.md, keybindings.json and history.jsonl in the new folder to the ones in ~/.claude, if they exist there (on Windows this needs Developer Mode; if it is off, copy them instead and tell me).
5. Never move, change or delete anything inside ~/.claude. Never read, copy or move .credentials.json, .claude.json or any token or key.
6. Do not sign in for me. Show me the command I run myself to sign in the new account:
   macOS/Linux: CLAUDE_CONFIG_DIR=~/.claude-accounts/work claude auth login
   PowerShell:  $env:CLAUDE_CONFIG_DIR="$HOME\.claude-accounts\work"; claude auth login
7. Show me how to start Claude with that account later (the same variable, then claude), and that leaving the variable unset uses my current account.
8. Finish by listing every link you made and the folder it points to.

Skills, plugins, agents, commands, sessions, memory, plans and the symlinked settings are then shared live. MCP servers added with claude mcp add (and copied files) do not stay in sync by themselves; Agent Optics keeps those identical across accounts and handles switching.

Privacy

Everything stays on your machine. Agent Optics reads each agent's own sign-in, from the folder you choose, to ask that provider for your usage, and sends nothing anywhere else: no telemetry, no cloud sync. Keys and cookies you paste are stored in your system keychain through the editor. History is kept locally for 90 days and deleted when you remove an account.

Claude Code logins stay in Claude's own files: each extra Claude account gets its own folder, signed in by Claude itself, that links to your shared Claude folder. Extra Codex logins are kept in your system keychain and swapped in when you switch.

Agent Optics never signs you in and never renews a sign-in: it only reads the token each agent already keeps. The one exception is a Codex switch you ask for, which swaps in the login Agent Optics kept for that account. When a token has expired, the card asks you to start that agent once (it renews its own sign-in) and keeps the last numbers until then.

Good to know

The usage numbers come from the same endpoints the agents' own CLIs and dashboards use. They are not public APIs and can change without notice; when that happens Agent Optics keeps your last reading, marks it as cached, and falls back to local session logs where possible.

Settings

License

MIT. Bundled open-source components and their licenses are listed in THIRD_PARTY_NOTICES.md.