marinsokol5

Agent Manager — Development skill for Claude Code

Development community

macOS menu-bar app + CLI for juggling multiple Claude Code and Codex accounts on one machine — isolated logins, parallel sessions, live usage tracking, and scheduled usage-window warm-ups.

How to install Agent Manager

This entry records only its repository, not the path inside it, so there is no exact command to give. Open marinsokol5/agent-manager and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Agent Manager does

macOS menu-bar app + CLI for juggling multiple Claude Code and Codex accounts on one machine — isolated logins, parallel sessions, live usage tracking, and scheduled usage-window warm-ups.

Alternatives in Development

  • Claude Balancer — A load balancer proxy for multiple Claude OAuth accounts with automatic failover, request tracking, and web da 910 ★
  • Cc Bar — Native macOS menu bar app: track quota, usage and cost for Codex (multi-account) and Claude Code, from your me 119 ★
  • CoderBar — Native macOS agent control for Codex and Claude — monitor, approve, ask, and jump back from the menu bar 100 ★

README

Agent Manager

A macOS app for juggling multiple Claude Code and Codex accounts on the same machine.

It lets you run each account as a separate agent session, keep an eye on how much usage each one has left, and warm up an account's usage window to increase the number of tokens available.

What

1. Run any account independently

![Agents screen: each account listed with its provider, connection status, and remaining usage](screenshots/agents-view.png)

am run  []

This starts a `claude` or `codex` session under that account's own isolated config home and hands your terminal to the CLI. Your normal `~/.claude` / `~/.codex` login is never touched.

Each account's home symlinks back to your real `~/.claude` / `~/.codex` for everything except the per-account identity file (`.claude.json` and `auth.json`), so accounts share the same settings **and the same session history**. That means you can pick a session back up under a different account — handy when one account's window runs out mid-task:

am run claude-ms55
# runs out of tokens
am run claude-ms18 --resume 

The **Source home** effectively groups accounts: everything pointing at the same folder shares settings and history, so you can run a few work accounts off one source home and your personal ones off another, fully apart.

2. Track usage at a glance

Track each account's usage from the menu bar ( individual menu bar entries or one collapsed) or from the CLI (`am usage`).

Menu bar — individual Menu bar — merged
Menu bar dropdown showing each account as its own entry with its usage Menu bar dropdown with all accounts </div> </section>  </div> <section class=

Related Skills