Accounts and usage

More than one account

An agent that supports it (Claude, Codex, Copilot, OpenCode) can have more than one signed-in account, each with its own home directory so the two logins never collide. Add one from that agent’s detail page in Settings > Agents: a name, an optional folder, and a real terminal tab running the vendor’s own sign-in. Removing an account you asked Tori to create deletes its sessions along with it; removing one you pointed at a folder you already had only forgets it, the folder and its login stay exactly as they were.

The account you never explicitly set up, your existing login from before Tori, always stays available too; Tori never copies or stores its credentials.

Limiting agents per project

A project can be limited to the agents and accounts you pick, so a client’s repo only ever runs on that client’s login. Right click the project in the sidebar and choose Agents, switch from Every agent to Only selected, and tick the agent and account pairs it may use, for example Claude on your work account and nothing else. The item only shows up once you have more than one agent or account to choose between.

Any other agent or account is refused before a session starts or resumes, with a note saying which pair is not allowed in this project. The rule follows the folder, so every worktree Tori makes under the repo inherits it, and a repo nested inside another project uses its own rule. A project with no rule allows every agent you have configured.

Put your client projects in their own spaces (see Spaces) and keep a personal space whose projects have no rules. The git host side is picked per repo too: see Pull requests and issues.

Usage and quota windows

Where an agent can report it, a titlebar strip shows a live bar per account: click it to pin open a card with every window that account can answer for, its plan, and when it resets. Usage comes from up to three sources, each one filling in what the last one could not answer: the agent’s own session events, a bounded read through its CLI, and, only if you opt in per account, a read of its OAuth token from the system keychain. That third source is never on by default, since it is the most invasive: a single explicit toggle per account, not a background setting.

Per account, in Settings > Agents, you can choose which usage windows show in the titlebar, set a warn threshold, and turn on a notification for when that threshold is crossed and when a window is fully spent.

What Tori does not do

There is no historical usage chart. A quota window belongs to the account, not to Tori, so a chart built only from what Tori itself has observed since you opened it would be mostly gaps. What you get instead is always the number the agent, or its vendor, is willing to answer for right now.