orchestra / docs
Documentation/Workspace

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 profile

A 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

  1. Open Settings → Profiles and choose New Profile…, then give it a name and, optionally, an emoji.
  2. 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.
  3. 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.

Browse documentation

Welcome to OrchestraA macOS and Linux workspace for your projects, terminals, and coding agents.
InstallationDownload Orchestra from GitHub Releases, or build it from source.
Projects & sessionsOrganize your work around folders, with an isolated worktree and terminal for every session.
Supported agentsUse the agent CLIs you already know, with their own configuration and credentials.
ProfilesUse different Claude Code and Codex accounts, such as work and personal, in the same workspace.
TerminalA real interactive terminal, running your agent or shell in its own folder.
Sidebar & navigationArrange the sidebar, switch projects with Arc Mode, and keep track of activity.
Saved workspace & resumeReturn to your projects and continue a captured agent conversation.
Issues & pull requestsRead and triage repository context, then start an agent session without leaving Orchestra.
Session messagingExchange requests and replies between existing sessions in the same project.
AppearanceChoose a palette for the whole workspace, including your terminals.
Custom themesCreate your own palette in a JSON file and use it beside the built-in themes.
UsageSee subscription limits for your agents and OpenRouter spend by model.
Settings & storageGeneral preferences and where Orchestra keeps workspace metadata and message history.
Privacy & usage dataOptional anonymous usage sharing, approximate city and country, and every collected event.
Keyboard shortcutsThe everyday actions you can reach from the keyboard.
ContributingReport issues, propose changes, and build Orchestra locally.
FAQAnswers to the questions that come up before your first session.
↑↓ Navigate↵ Openesc Close