Provider accounts

Synara supports multiple accounts for each provider. Each account has its own model-picker tab and launch configuration, so work and personal accounts can share a workspace without sharing the selected runtime environment.

Add and sign in

Open provider settings and choose Add account. Choose the provider and an optional display name and color. Configure its account directory or environment as needed. Import directory references an existing directory without moving or copying it; browser clients must configure a server-side path manually.

Choose Sign in on that account. Synara opens an interactive terminal in settings, using that account's executable and environment on the Synara server machine. Complete the provider's browser, device-code, organization, or credential prompts yourself. For Pi and Oh My Pi, use Sign-in options after startup prompts.

Closing the dialog stops the sign-in process and clears its terminal history. It does not log out an account whose credentials the provider already saved. Synara shows Authenticated only after a supported health check confirms it; an unknown status may require checking the provider directly. OpenCode accounts using an external server authenticate on that server.

Pick models and switch accounts

Choose the account's tab in the composer model picker. Models come from the installed runtime and account configuration. Synara refreshes stale catalogs when needed and keeps a previous working catalog available if discovery fails; use the retry action when an error is shown.

Favorites retain model, effort, speed, and account together. A favorite for a disabled or removed account is hidden. To continue an existing conversation with another provider, use a provider handoff.

Inspect account usage

The Environment panel shows accounts for the active provider with separate usage details. Settings → Usage uses account-specific snapshots too. Availability depends on what each provider exposes; an absent account metric must not be interpreted as zero use.

Use account commands in Synara terminals

Enabled accounts receive stable commands such as claude-work or codex-personal in new or restarted Synara terminals. Ordinary claude and codex commands keep their meaning. Synara does not edit your global shell startup files.

Account commands support directory-backed credentials. Secret environment values are not written into their command files; a terminal command that needs such a secret still requires it through a secure runtime mechanism. Managed Synara sessions use the account's configured environment.

Provider capabilities still differ. See the provider guides for runtime setup and troubleshooting.