Profiles
Use different Claude Code and Codex accounts, such as work and personal, in the same workspace.
On this page
A set of agent accountsAdd a profile and sign inChoose a profile for your sessionsA fresh configurationUsage by profileRemove a profileA set of agent accounts
A profile is a named set of agent accounts. Sessions in the same project can use different profiles, so you can keep work and personal usage apart without signing out of anything.
Default is the accounts each CLI uses outside Orchestra. Every other profile has its own Claude Code and Codex configuration folders under ~/.orchestra/profiles, and Orchestra points the CLIs at them when a session starts. Other agents cannot choose an account yet, so they always use Default’s.
Add a profile and sign in
- Open Settings → Profiles and choose New Profile…, then give it a name and, optionally, an emoji.
- Beside Claude Code or Codex, choose Log In. Orchestra opens a terminal session in the selected project that runs the CLI’s sign-in, and you complete it there.
- The profile shows Logged in for each account. Use Log In Again to switch accounts later.
Orchestra never reads credential files; it only asks each CLI whether it is signed in.
Choose a profile for your sessions
Each project chooses the profile its new sessions use, in Edit Project… or in the project menu under Profile for New Sessions. The New Session dialog starts on that profile and can choose another.
A session keeps its profile for its whole life, including when you resume it. In the sidebar, a session whose profile differs from its project’s shows that profile’s emoji or initial, and the status bar names the profile of any session outside Default.
A fresh configuration
A new profile starts without Default’s CLI settings, MCP servers and skills. Settings → Profiles shows when a profile is missing the Orchestra Skill and installs it with one click.
The profile’s folders are set after your shell’s rc files load, so an rc file that sets CLAUDE_CONFIG_DIR or CODEX_HOME does not switch an agent session’s account. In a plain Terminal session, it still can.
Usage by profile
Settings → Usage has a Profile menu that shows the Claude Code and Codex limits of each profile. OpenRouter uses one management key for every profile. See Usage.
Remove a profile
Choose the trash button beside a profile. Projects that use it move to Default. Sessions that used it can no longer be resumed, so they never switch account. Its sign-ins and conversations are kept on disk in ~/.orchestra/profiles.