macOS app
The desktop workspace where your agents, tasks and designs work from the same understanding of your product. This page is about the app itself: what ships inside it, how the first run goes, and what it needs from your Mac.
Studio is not a chat window with panels bolted on. The things you reach for while building sit in the same app, around the conversation.
Chat that splits and detaches
Threads open as tabs, split into panes, and detach into their own windows. A multi-device stage runs your app next to the conversation.
Source control that lands the work
Switch checkouts, read the per-file diff, stage and commit, then land a branch as a merge or a pull request. Studio runs git itself, never the model.
Terminal and run output
The command you need is in the same window. An integrated terminal and a run panel, so you are not switching apps while an agent is mid-task.
Patterns, MCP servers, usage
Everything an agent can reach, in one place. Import a ready-made bundle at a path, manage the MCP servers and extensions, and watch usage against your plan.
Knowledge authoring, with review
Write memories, rules and skills at the path they belong to, with comments per item. Agents propose an append or a targeted replace rather than rewriting a body.
Dictation
Hold to talk instead of typing, across 90+ languages, with an on-device macOS engine behind it. Nothing listens in the background.
No separate service to install and no MCP wiring to maintain. This is what happens between opening a thread and the agent acting.
01
You open a thread
In a directory the workspace is attached to, so the runtime knows which path the work is on.
02
The hook supervisor reads the cache
A precomputed index of the memories, rules and skills pinned at that path and the ones above it.
03
The engine starts already knowing
The slice is in context before the first tool call, with no round trip to fetch it.
Studio also bundles the MCP server your assistant speaks to, companion file sync for CLAUDE.md and AGENTS.md, and schedules that wake it up on their own.
What you can actually build with Studio is laid out capability by capability on the features page. These are the parts of the app itself.
Every capability, one page
Chat, Tasks, Design and Signals, each with its own block and its own docs.
The desktop surface
The full reference for Studio: surfaces, what is bundled, first run and coexistence.
Isolated branches
Give a conversation or a card its own checkout, then land the branch from Source Control.
Running several agents
A tab per engine on one workspace, each with its own run state.
Schedules
Run a brief on a repetition against a card, a design, or nothing at all.
The iPhone app
What you can do from the phone, and what stays on the Mac.
Free for individual use. Your first memory takes a minute, and the next session starts from it.
