Studio Overview
The visual workspace for composing, inspecting, and running DOT-based AI systems.
If the CLI is the fastest way to install and publish, Studio is the best way to see what you're building.
Use Studio when you want to:
- Compose performers visually from Tal, Dances, and models
- Build and edit multi-performer Acts
- Manage drafts with a rich UI
- Run work in direct or safe mode
Launch Studio#
One-line launch#
npx dot-studio .
Global install#
npm install -g dot-studio
dot-studio .
Useful flags#
| Flag | What It Does |
|---|---|
--no-open | Start without auto-opening the browser |
--port 3005 | Use a custom port |
Studio opens in your browser and uses the project directory as the working Workspace.
Why People Use Studio#
Most AI tools hide the real setup behind one model picker and one prompt box. Studio takes the opposite approach:
| Traditional AI Tool | DOT Studio |
|---|---|
| Hidden system prompts | Performers are visible objects |
| No safety net | Safe mode built into the product |
| Copy-paste to iterate | Drafts can move toward publication cleanly |
| Single-agent only | Multi-performer choreography is explicit |
Studio is a workspace for designing and operating AI behavior, not just chatting with a model.
The Main Pieces of the Interface#
Canvas#
The canvas is where your performers and acts live. You can:
- Place performers and acts
- Drag items to organize your layout
- Inspect and edit selected items
- Save layout as part of the Stage
Asset Library#
The Asset Library gives you access to local assets and drafts:
- Browse installed Tal, Dance, Performer, and Act assets
- Inspect draft content
- Drag assets onto the canvas
Inspector#
The inspector changes based on what you select. Use it to configure:
- Performer Tal and Dances
- Model and model variant
- Execution mode (direct vs safe)
- Act participants and relations
Chat and Thread Views#
Studio supports both runtime surfaces:
| Surface | Use For |
|---|---|
| Performer Chat | One performer at a time — standalone conversations |
| Act Threads | Multi-participant choreography — collaboration scenes |
Your First Useful Workflow#
1. Start with a project that already has DOT assets#
dot init
dot install performer/@acme-platform/agent-presets/sprint
npx dot-studio .
2. Inspect imported assets#
Open the Asset Library and confirm your local workspace is visible. This is the quickest way to understand what's already available.
3. Create or adjust a Performer#
Add a Performer to the canvas and configure:
- Tal (identity)
- One or more Dances (skills)
- Model selection
- Direct or safe execution mode
4. Run a standalone conversation#
Use a Performer directly when you want a single role to work on a task:
- Coding help
- Review help
- Writing help
- Structured analysis
5. Build an Act when one role isn't enough#
Create an Act when you want multiple performers to collaborate explicitly:
- Planner + Implementer
- Lead + Reviewer
- Incident commander + Specialist
Workspace: The Saved State#
A Workspace is the saved Studio state for one working directory. It includes:
| Component | Description |
|---|---|
| Performers | Placed and configured on the canvas |
| Acts | Multi-performer collaboration setups |
| Drafts | Work-in-progress assets |
| Layout | Canvas arrangement and positions |
| Runtime config | Direct/safe mode, model selections |
In practice, the Workspace is the main thing you're editing whenever you use Studio.
Drafts and Local Authoring#
Studio is not only for consuming published assets — it's also a great place to author and iterate:
- Create drafts directly in the project
- Revise performer configuration visually
- Evolve an imported asset into a project-specific draft
- Move from draft to published asset later through the CLI
Safe Mode vs Direct Mode#
Studio supports two execution modes — one of the most powerful features of the platform.
Direct Mode#
Runs against the real working directory.
| Best for | Avoid when |
|---|---|
| Trusted, low-risk edits | Changes are risky or large |
| Quick iteration | You want to review before applying |
| Easily reversible work | Multiple files might be touched |
Safe Mode#
Runs against a shadow workspace with review before apply.
| Best for | Avoid when |
|---|---|
| Risky refactors | Work is trivial and trusted |
| Large AI-assisted edits | Speed matters more than safety |
| Review-first workflows | You don't need an approval step |
Why this matters: Safe mode is one of the clearest reasons to choose Studio over a plain chat-first interface. You get freedom to let the AI work, plus a review step before anything touches your real project.
This avoids the common problem of hidden configurations.
When to Use Studio vs CLI#
| Goal | Studio | CLI |
|---|---|---|
| Visual composition | ✓ | |
| Safe mode review | ✓ | |
| Multi-performer collaboration | ✓ | |
| Draft-heavy iteration | ✓ | |
| Runtime inspection | ✓ | |
| Fast install | ✓ | |
| Search and list workflows | ✓ | |
| Publishing | ✓ | |
| Scriptable terminal usage | ✓ |
Recommended Next Pages#
| Page | What You'll Learn |
|---|---|
| Performer Composer | Build and configure performers visually |
| Act Editor & Runtime | Multi-performer choreography |
| OpenCode Runtime | How Studio's execution engine works |