Settings

Settings holds everything that applies to the whole studio: your Claude and ElevenLabs connections, the database, and checks that this computer can build and render videos. Product-specific settings, such as brand and modules, live in Workspace settings instead (see Workspaces).

Open Settings from Settings in the sidebar, or press ⌘ , (on Windows/Linux Ctrl ,).

#The status pill and checks

The header shows a status pill that sums up every check:

Click Check again to run all checks now. Checked HH:MM shows when they last ran.

Each tab lists its own live checks. A check that fails or warns shows how to fix it and, where it helps, a command with a Copy button. Paste the command into Terminal (macOS, Linux) or PowerShell (Windows), run it, then click Check again.

#Key fields

The Claude and ElevenLabs tabs each have a key field. They all work the same way:

• Paste a key and save it. Keys are stored in your computer's password store and only sent to Anthropic and ElevenLabs. They're never shown in full again.
• A saved key shows as Saved …abcd (its last four characters), with Replace and Remove.
• If DemoVexa found a key in its configuration file instead, it offers Save to keychain to move it into the password store.
• The eye button shows or hides what you've typed.

See Privacy and your data for where keys are stored on each system.

#Tabs

#Account

Your DemoVexa account on this computer: who's signed in, your plan and its status, this month's new videos and renders against your allowance, and what the plan includes. From here you can Open billing, Manage computers, Check plan now, or Sign out of this computer. Signed out, it shows Sign in to DemoVexa. See Your account and computers.

#Claude

• Connection: click Test connection to check that DemoVexa can reach Claude.
• How Claude runs:
  • My Claude login uses Claude Code signed in with your Claude account. It's for your own use only; selling videos or sharing the studio with a team needs an API key.
  • Anthropic API key: every call is billed to the API key, at API prices.
• Anthropic API key: the key field, used when Claude runs with an API key.
• Model:

Checks: Connection, Claude Code, API key, Model, Agent permissions.

#ElevenLabs

• ElevenLabs API key: the key field.
• Default voice: Studio default (Sia) or any of your ElevenLabs voices. It's used when a project hasn't picked a voice.

Checks: API key, Plan (warns when fewer than 5,000 characters are left), Default voice, Model.

#Database

The Local database card has Back up now and Show in folder, and shows:

• Status: the database type and size.
• File: where the database is. To keep it on another drive, see Privacy and your data.
• Contains: counts of what's stored.
• Backups: the newest 5 backups, plus how many older ones there are.

Checks: Database, Migrations, Backups, Storage (warns when less than 5 GB is free). See Backups.

#Rendering

This tab has checks only. They cover what DemoVexa needs to build and render videos: Video repo, Repo packages, Studio packages, Node.js, FFmpeg, Chrome Headless Shell, Photo conversion and Keep awake. On Linux it also checks the Chrome libraries and the folder picker.

#Folder access

DemoVexa tests that it can write, read and delete files in four places: Studio data, Video code, Video assets and Previews and stills. If a test fails, the check shows the fix for your operating system. See Troubleshooting.

#Studio

Checks: Address, Password, Settings files, Work in progress.

Under Setup, Run setup again reopens the first-run setup window, so you can walk through connecting Claude and ElevenLabs, the system check, and adding a product again. See First run.

#Workspace keys

By default every workspace uses the studio's Claude and ElevenLabs keys from Settings. A workspace can use its own keys instead, set in Workspace settings → Connections. See Connections and checks.

#Related

• Privacy and your data
• Backups
• Troubleshooting