Skip to main content
Settings controls how Studio looks, how tabs behave, how the terminal responds, how Copilot thinks, and what happens when you sign out. Most choices are per-user and follow you across devices once you sign in, so you can pick a theme and a default model on your laptop and see the same setup on your desktop. The settings surface is organized into Workspace, Appearance, Terminal, AI, and About. Use Workspace for the IDE shell, Appearance for theme and type, Terminal for session behavior and safety, AI for Copilot defaults, and About for platform, version, and update checks.

Workspace

Workspace settings control the IDE shell itself: tab close buttons, preview mode, modified-tab highlighting, split-on-drag, status bar visibility, and whether Zen mode hides the status bar. Use Workspace first when Studio feels visually noisy or tabs keep replacing each other. Turning off preview mode makes every opened item persistent; leaving preview mode on keeps browsing fast when you are searching through hosts, files, and memories.

Appearance

Studio ships with light and dark modes and a small library of presets. You can also set exact colors with the color wheel and a contrast slider. If you rely on your OS for dark mode at night, follow system is the friendliest setting. If you share screens in calls, nudge contrast up a little so viewers on lower-end displays can read along. Themes can be imported, exported, or reset. Export a theme when you want a team-standard look for shared screens or training environments.

Terminal

Terminal settings are grouped into expandable sections so you can tune the session surface without hunting through unrelated preferences. Terminal settings are operational settings. Change them when they help your day-to-day flow, then keep them steady during incidents so recordings, shared sessions, and teammate expectations line up.

AI

The AI section controls the default model, high-autonomy behavior, run length, chat suggestions, and access to AI memories.
YOLO mode is intentionally high-trust. Leave it off for production devices unless you have already constrained the target, credentials, and blast radius.
The response mode menu in Copilot is still the place to pick Default, Ask, or Planning for a particular conversation. Settings > AI decides the defaults and upper bounds that new agentic work inherits.

AI usage

The AI usage page shows token counts, a cost estimate, and a per-organization breakdown over the period you pick. It’s the page to open when you want to see where spend is going — a verbose procedure, a long investigation, or a teammate running high-autonomy sessions will all stand out here.

About and updates

The About section shows your platform, the Studio version, and update status. Use Check for Updates when support asks for your version or when you want to confirm you are on the latest desktop build before a maintenance window. Studio checks for updates in the background. New versions download silently; a toast tells you when one is ready to install. You choose when to restart, so an update never interrupts an active session.

Storage and cache

Studio keeps a local cache of your workspace so you can work while offline. When you come back online, the cache reconciles with your organization and the two converge. The cache is rebuilt from scratch on sign-out and repopulates from your organization the next time you sign in, so you don’t have to think about it day-to-day.

Sign out

Signing out clears local credentials and the decrypted cache from your machine. Your synced organization data stays in the cloud. Signing back in restores the workspace — the same hosts, the same team procedures, the same memories — as soon as the cache rebuilds.
If you’re handing a laptop to someone else, sign out first. The sign-out flow is the cleanest way to remove your access without deleting the app.

AI Copilot

Pick modes, set approval posture, and learn what Copilot can see.

Security and privacy

See what’s encrypted, what leaves the machine, and how sign-out clears state.