Skip to content

Profile and account reference ​

Profiles and LLM accounts are stored in the database. Manage them in Settings or through the profile and account APIs.

Profile fieldValue
nameRequired unique name. Immutable after creation
harnessInherited from the account. codex
account_idAccount UUID. Can be changed to another account of the same harness
modelRequired model ID. A session can override it with agent.model
descriptionOptional description
activePermits new sessions when the account is also active
instructionsShared instructions. Replaced by agent.instructions
codex.effortnone, minimal, low, medium, high, xhigh, max, ultra
codex.summaryauto, concise, detailed, none
codex.personalitynone, friendly, pragmatic
codex.service_tierOptional nonblank provider service-tier name
Account fieldValue
idGenerated UUID. Identifies the account in sessions and quota observations
nameEditable display name
harnessImmutable. codex
auth_modeImmutable. api_key or account
activePermits new sessions through active profiles
credential_storeImmutable store name for account-file authorization
api_keyWrite-only provider key. Responses expose only api_key_mask
auth_fileAuthorization JSON supplied when creating an account-file account. Edit through the authorization-file API

API-key values are encrypted in the database. Account files are stored in S3. Runtime TOML contains only infrastructure such as credential stores and services.

Credential store access ​

Supply S3 credentials to API and worker through AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. See account authentication to prepare the store and authorization file.

Credential store fieldValue
types3
bucketBucket name
regionRegion, defaults to us-east-1
endpoint_urlOptional custom S3-compatible service URL

Codex option support depends on the selected model and credentials. Orpheus captures settings when creating a session. The public API cannot override codex.effort or other codex options. Select an appropriate profile instead.

Profile examples · Authentication