Settings tabs
The beta settings app currently routes across these tabs:
ProfileBillingClaimsBYOKIntegrationsWorkspacesAPIEditorStorage
Profile
The profile section includes:
- display-name editing
- password change
- account deletion
The deletion flow explicitly warns about subscription state and requires confirmation.
Billing
Billing currently handles:
- current credits
- subscription tier status
- subscription renewal/cancel timing
- checkout initiation
- billing portal session creation
- credit pack listing
AVS uses the same credit balance across editor features, generation, rendering, and the public API.
Claims
The settings app contains a claims surface used for one-time or promotional credit claims such as signup bonus flows.
BYOK
Bring-your-own-key settings currently model these providers:
- OpenAI
- Anthropic
- ElevenLabs
The UI also tracks provider summary state such as:
- whether encryption is available
- whether a credential exists
- last update time
- key hints and service-account metadata where relevant
Use this tab when you want provider access separated from the app’s default configured credentials.
Integrations
The integrations tab currently includes:
- Telegram linking and unlinking flows
- CLI token management
The CLI token surface supports creation and revocation for device and recorder workflows.
Workspaces
The workspace settings tab includes:
- listing workspaces
- creating workspaces
- invite management
- member management
- leave/delete actions
- workspace studio configuration
This is the operational home for shared-team administration.
API
The API tab is specifically for public API access tokens.
These tokens are for the public /api/v1/* routes and are distinct from CLI tokens.
Supported token actions include:
- create
- list
- rotate
- revoke
Editor preferences
The editor settings tab manages product preferences such as:
- editor appearance and behavior
- notification-related preferences
- collaborator cursor visibility
- studio settings normalization-backed preferences
This is where users tune the experience without changing project content.
Storage
The storage tab has two different scopes:
Local app storage
This section inspects browser-side AVS storage usage and can clear:
- local project binaries
- project JSON stores
- browser cache namespaces used by AVS
Workspace storage
Admins can inspect and configure workspace object storage:
- bucket
- region
- endpoint
- access-key hint
- secret state
- force-path-style setting
The UI explicitly handles managed, external, and misconfigured states.
Recommended operating model
- Keep account and billing separate from workspace administration.
- Use BYOK only when you need provider isolation or custom billing ownership.
- Keep CLI tokens and public API tokens separate.
- Be careful with storage overrides because they affect future asset routing behavior.
