diridiri can remember more than one Claude Code or Codex login, such as work and personal, and switch every open tab of that agent between them. It also estimates what you spend from the agents' own transcripts and shows how much of your plan's limits you have used.
Account profiles
A profile is a saved login for one agent on one machine. diri reads who each login belongs to from the login itself, and shows its email, its plan (such as Max 20x or Pro) and how much of its plan limits it has used.
Open Settings → Accounts, or choose Manage accounts… in the account menu at the bottom left of the sidebar.
| Action | What it does |
|---|---|
| Save | Shown next to a login that is in use but not saved yet. Keeps it as a profile named after its email. It does not switch accounts. |
| Add Claude Code account, Add Codex account | diri opens a login-only tab; finish the browser login there. The new profile takes its email's name when the login lands, and does not change the active login. |
| Sign in | Signs a saved profile in again, for example after the provider signed it out. |
| Rename, Remove | Removing a profile leaves its saved login in place. |
Profiles for a remote host, or older profiles with a folder of their own, are under Other profiles in Settings → Accounts, with Run on and Use by default for this Agent on this host.
Switch accounts
Click an account in the account menu at the bottom left, choose Switch in Settings → Accounts, or type its name in the command palette (⌘K). diri then:
- Stops that agent's conversations open in tabs and split panes.
- Installs the selected login.
- Resumes the same conversations on the new login. Sleeping tabs restart and go back to sleep. Stopped tabs stay stopped.
- Makes that account the default for new tabs.
When the account in use is running low, Settings → Accounts and the command palette mark the account with clearly more room Most room. An account whose full limit window has reset since diri last saw it is marked Ready.
Nothing is copied or migrated. Conversations, MCP setup and settings stay in the agent's usual home folder (~/.claude or ~/.codex).
| Agent | How the switch works |
|---|---|
| Codex | Swaps only auth.json in ~/.codex. Open tabs relaunch with codex resume <thread>. |
| Claude Code | Each profile owns a private credential store, so no tokens are copied. Open tabs relaunch with claude --resume <conversation>. A tab that has not saved a transcript yet starts fresh with the same conversation id. |
Things to know
- A switch is never refused because of one tab. A Codex tab diri cannot identify keeps the previous login and is reported. It switches the next time it restarts.
- Closed and archived sessions are not restarted. They use whatever login is current when you resume them.
- Agent processes started outside diri are not restarted and may keep their cached login.
- Hosted connectors are tied to the provider account, not to files on your Mac. After a switch, a connector such as Slack can show as not installed until you connect it on the selected account.
- Codex switching works with Codex's file credential store. If Codex is set to use the Keychain or another backend, the switch stops with an error before changing anything.
- Editing or removing a profile affects future launches. Running sessions keep their account. Removing a profile leaves the provider's files and credentials in place.
- Before the first switch, Claude Code tabs use Claude's own login. Switching away from it first saves its latest tokens into the profile saved from it, so switching back finds a working login.
Where logins are stored
Profiles are kept in accounts.json next to the Engine's socket, in ~/Library/Application Support/Dirijor on macOS. Saved Codex logins live under codex-logins/ and Claude stores under claude-logins/ in the same folder. Everything is owner-only.
These files are credentials. Protect the folder like the agent's own login file. diri never returns them in responses, logs them or passes them as command-line arguments. Before replacing a Codex login it keeps the previous one in codex-logins/previous-auth.json.
Usage and cost
Open Settings → Usage to see tokens and estimated cost over a date range.
| Source | How it is counted |
|---|---|
| Claude Code | Read from local and remote transcripts, priced at diri's bundled model rates. |
| Codex | Read from local and remote transcripts, priced at diri's bundled model rates. |
| Cursor | Billed usage from Cursor's dashboard, when you are signed in on this Mac. |
The page shows processed tokens, cached and uncached input, output, and cache read savings, compared with the previous period of the same length. Switch between This Mac and All machines to include remote hosts.
- Transcripts are included even for sessions you ran outside diri.
- Claude and Codex costs are estimates at API rates, not your bill. Usage on an unknown model is left out of cost.
- Cache read savings compare cached reads with uncached input rates. Cache write premiums are excluded.
- Remote hosts refresh every 5 minutes over SSH. Only totals cross SSH. An unreachable host keeps its last saved totals.
Click Share to make an image of your usage. You can pick cost or tokens, the graph, a per-agent breakdown and a theme, then copy, save or post it.
Plan limits
Settings → Accounts shows every plan window of every saved account, such as the 5-hour and weekly limits, and when each resets. The account menu at the bottom left shows the windows of the accounts in use. Limits refresh when you open the menu or that page. A meter marked stale has passed its reset time or could not be refreshed.
diri asks the provider only while an account's short-lived access token is valid, and never refreshes a token itself. An account you have not used for a while shows its last known numbers, dated ("as of 4h ago"), or Not checked if diri has not been able to ask yet. diri keeps those numbers in account-limits.json next to its other files: percentages and reset times only.
For a Claude account, diri also asks Anthropic whose the token is. It shows the numbers under that account, and Save names the account after it. The account recorded beside a Claude login can be out of date after a switch, because any Claude Code session still running can write its own account back.
These numbers come from the provider for each signed-in account. They are separate from the cost estimates above. Sign in again means the provider no longer accepts that account's saved login.