Questions

Short answers, with a link to the page that has the detail.

Getting Studio

Is Studio free?

Yes. Studio is free and needs no plan: the desktop app runs on macOS, and its server package on Linux. Its agents run on your own provider accounts, so what they use counts against those accounts, not against Kelrova. See Pricing.

Do I need a Kelrova scan plan?

No. Studio does not need a plan for Kelrova's cloud security scans. If your organization has scans, chats can also work on their findings; see Kelrova findings in Studio.

Which computers does it run on?

The desktop app runs on macOS with Apple Silicon and on Linux x86_64 and ARM64. A Linux server can also run Studio without a screen, installed with one command. See Install on macOS, Install on Linux and Server requirements.

Do I need an account?

You can choose Continue without an account and use Studio on one computer. Signing in to your Kelrova account adds sync between your devices, remote devices and support from the app. See Sign in and approve this computer.

Agents

Which agents can I use?

Claude Code, Codex, Cursor, Devin and Grok, among others. Settings → Agents lists every agent a device supports and whether it is installed. See Connect your agents.

Can I use several provider accounts?

Yes. Each agent can hold several accounts, and you pick which one it uses. In an Orchestra, agents run in parallel, each under its own account and quota. See Models, reasoning and accounts and Mix providers and accounts.

How do I see what a chat cost?

Open Context usage from the ring in the composer. It shows the chat's estimated cost at published API list prices, split by agent. Subscription plans bill differently. See Token usage.

What happens when I hit a usage limit?

The turn stops with a row such as Session limit reached. By default Studio waits for the limit to reset and retries, if the reset is within five hours. See Troubleshooting.

Where work runs

Where do sessions run?

On the device that holds the project: this computer, or a remote device you added. The agent, its checkout, the terminal and the browser all run there. You pick the device when you start a chat. See Start sessions on a server.

What happens when my Mac sleeps?

A session on a remote device keeps going, because it runs on that device and not on your Mac. A session on your Mac runs on your Mac, so it cannot make progress while the Mac sleeps. To keep long work going with the laptop closed, run it on a server. See Run Studio on your own server.

Can I send to a device that is asleep?

Yes. Studio tells you the device is offline, and the message starts once it reconnects. A scheduled chat whose time passes while its computer is asleep or offline starts when it is back. See Device status and Scheduled chats.

Who can work on my devices?

From another device, only devices you approved can run, steer or stop a session, read protected content or open a terminal. See Approved devices and signatures.

Data

What leaves my computer?

Your agents talk to their own providers under your accounts. When you are signed in, Studio syncs your workspace and chats between your devices; chats, previews, memories, settings and automations are encrypted before they sync, and only paired devices with a key can read them. See What stays on your computer and what syncs and Encryption of synced content.

Can I back up my settings?

Yes. Settings → Backup & restore exports preferences, guidelines, subagent profiles, enabled agents and project memory to a JSON file. Chats and credentials are never included. See Backup and archived chats.

What does a problem report send?

Your subject and description, and, if you keep them, diagnostics you read in full first: recent app logs and a device summary with email addresses, tokens, your home folder and message text removed. See Report a problem.

How does Studio update?

Every release is signed, and Studio checks the signature before it updates itself. The desktop app never installs an update on its own: you choose when to restart. A server installed with the install command keeps itself up to date. See Signed updates and Keep servers up to date.