claude-accounts-dash

A local dashboard for people who use more than one Claude account.

See every account's usage limits at a glance, browse all your Claude Code sessions, and when one account hits its limit, export the conversation so you can paste it into a new session on another account and keep going.

• Private: reads files that are already on your computer. Nothing is uploaded, and the server only listens on 127.0.0.1.
• Lightweight: pure Python standard library, with no dependencies. It starts in a few seconds.
• Cross-platform: Windows, macOS and Linux, Python 3.9+.

Unofficial community tool. Not affiliated with or endorsed by Anthropic.

_{Screenshots use generated demo data.}

Contents

• Install
• Usage
• What's in the dashboard
• Screenshots
• Continuing a session on another account
• Platform support
• Where the data comes from
• Configuration
• Troubleshooting
• Development

Install

With pipx (recommended: it installs the command in its own isolated environment):

pipx install claude-accounts-dash

Or with pip:

pip install claude-accounts-dash

Install the latest version straight from GitHub:

pipx install git+https://github.com/erenkarakoc/claude-accounts-dash.git

Upgrade later with pipx upgrade claude-accounts-dash or pip install -U claude-accounts-dash.

Usage

claude-accounts-dash

The first start indexes your local transcripts, which takes a few seconds for hundreds of sessions. It then opens http://127.0.0.1:8765 in your browser. The page refreshes itself every 30 seconds, and only re-reads files that changed. Stop it with Ctrl+C.

python -m claude_accounts_dash does the same thing as claude-accounts-dash.

What's in the dashboard

Overview

• One card per account with its 5-hour and weekly usage, estimated reset times, and a chart of the last 24 hours.
• A "Use now" badge on the account with the most room left, and a warning when an account is currently blocked by a limit, showing the reset time Claude reported.
• Click an account's name to give it a nickname (for example "Pro #2 – work"). Accounts show a short ID until you do.

Handoff

• Every session that hit a usage limit, newest first, with an Export chat button. See below.

Sessions

• All sessions from all accounts. Search by title, folder or ID, and filter by account.
• Background sessions created by plugins are hidden unless you turn on Background.

Projects

• Every project folder with its sessions, prompts, tokens, disk size and the accounts that worked on it. Open shows the folder in Explorer, Finder or your file manager.

Activity

• Output, input and cache token totals, tokens per day split by model, prompts by hour of day, and each account's share of tokens.

Light and dark themes are available with the moon button.

Links like http://127.0.0.1:8765/#/activity open a tab directly, and #/handoff/export opens the export for the newest session that hit a limit.

Screenshots

Export a session that hit its limit, ready to paste into another account

Every session from every account

Activity: tokens per day by model, prompts by hour, tokens per account

Light theme

Continuing a session on another account

1. Open the Handoff tab and click Export chat on the session that hit its limit.

2. Choose what to export:

   Option	What you get	Typical size
   Full chat + Compact (default)	Every turn. Very long pasted prompts are trimmed, Claude's final reply for each turn is kept, and tool calls are summarized as "edited a.ts, b.ts; used 12x Bash".	Small to medium
   Last 5 / 10 / 25	Only the most recent turns, plus the summary Claude wrote when the chat was compacted, so the older part isn't lost.	Small
   Compact off	Everything, including every tool call.	Can be very large
   Brief	A short note: project folder, git branch, files touched, your last 5 requests, Claude's earlier summary, its last reply, and the path to the full transcript.	About 1k tokens

   The size (characters and approximate tokens) is shown under the preview.

3. Click Copy to clipboard, or Download .md.

4. In the Claude desktop app, switch to the other account and start a new session in the same project folder. The Open project folder button helps you find it.

5. Paste. The export starts with instructions telling Claude to check the project state, summarize where you left off, and continue.

The brief and exports are built locally from the saved transcript. Creating them uses no tokens.

Platform support

Account limits come from files written by the Claude desktop app. If you only use the Claude Code CLI (for example on Linux), the dashboard still shows sessions, projects, activity and exports. The limit cards will say No data, and sessions are grouped under the account recorded in the transcript where possible.

Where the data comes from

claude-accounts-dash never modifies Claude's files. The only file it writes is nicknames.json.

About the limit numbers: the desktop app records usage only while it is signed in to that account, so an account you haven't opened for a while shows its last known value. When the estimated reset time has passed, the dashboard assumes the window has reset and marks the value with ~. Reset times are estimated from the recorded samples; the exact reset time from Claude's "You've hit your limit" message is shown when one exists.

Configuration

Environment variables, all optional:

Troubleshooting

• "Port 8765 is in use": the dashboard is probably already running in another terminal. Open http://127.0.0.1:8765, or start another one with --port 8766.
• No accounts or limits shown: run claude-accounts-dash --paths to see which folders were found. On Windows, the Microsoft Store (MSIX) version of the Claude app stores its data in a private package folder, which is detected automatically since 0.1.4. If it still isn't found, point to it with CLAUDE_ACCOUNTS_DASH_APP_DIR. Limits need the Claude desktop app. Sign in to each account in the app at least once.
• An account's numbers look old: open the desktop app signed in to that account. It updates the usage history in the background.
• claude-accounts-dash: command not found after pipx install: run pipx ensurepath and open a new terminal.
• Unicode shows incorrectly in exports: exports are UTF-8. Open the downloaded .md in an editor that uses UTF-8.

Development

git clone https://github.com/erenkarakoc/claude-accounts-dash.git
cd claude-accounts-dash
python -m venv .venv
# Windows: .venv\Scripts\activate    macOS/Linux: source .venv/bin/activate
pip install -e .
claude-accounts-dash

Run the tests (they use a fake data folder, not your real one):

python -m unittest discover -s tests -v

Try it with demo data instead of your own (this is how the screenshots are made):

python scripts/demo_data.py demo-data

Then run the dashboard with these environment variables set: CLAUDE_ACCOUNTS_DASH_APP_DIR=demo-data/app, CLAUDE_CONFIG_DIR=demo-data/claude and CLAUDE_ACCOUNTS_DASH_CONFIG_DIR=demo-data/config.

Project layout:

src/claude_accounts_dash/
  server.py          reads local files, builds the data, serves the page and API
  static/index.html  the dashboard (plain HTML/CSS/JS, no build step)
tests/               smoke tests with fixture data
scripts/demo_data.py generates fake accounts and sessions for demos
docs/screenshots/    images used in this README

Releasing

1. Bump __version__ in src/claude_accounts_dash/__init__.py.
2. Create a GitHub release. The Publish to PyPI workflow builds and uploads it. One-time setup: on PyPI, add a trusted publisher for this repository with workflow publish.yml and environment pypi.

Or publish manually:

pip install build twine
python -m build
twine upload dist/*

License

MIT