A CLI for the people who hit Claude usage limits at 2am.

You buy Claude Pro for one account. You also have a work account on a different email. Codex is open in a third terminal. Each one has its own usage limit, its own session log, its own JSONL files buried under ~/.claude/projects/. Switching between them means rewriting environment variables and tailing four log files at once.

Rana is the tool I built after the third time I lost an afternoon to that.

Three commands

rana switch <tool> swaps ~/.claude to a different account profile by writing export statements you can pipe into eval. Each profile is isolated under ~/.rana/profiles/<name>/, locked to user read with chmod 600. A background scheduler polls every account every five minutes via claude --print "/usage" --output-format json, ranks them by remaining headroom in the five hour billing window, and recommends which one to use next.

rana agent reads Claude Code’s local session files directly. No API call, no auth, works offline. It renders a session tree, a tail of the active log, a status board of what every agent is doing right now, and a watch view that updates as new lines land. The cost numbers come from a small price table that knows the input, output, cache write, and cache read rates for Opus 4, Sonnet 4, and Haiku 4.

rana dash runs an Express server on localhost 4242 with four WebSocket panels: an agent tree, a task board, a log feed, and a detail pane. A usage strip sits at the top so the budget is always visible.

Version 0.1.0. No tests in the repo, no CI workflow. It’s a tool I wrote for myself and put on npm because somebody else might need it.