Active feature reference

Start and organize

• Scratch, folder, and repository project entry. New projects open in Build; switch to Design from the project header.
• Invisible General plus Research, Strategy, Creative Direction, private/project agents, and certified reviewer templates through the Agents panel and secure @agent invocation.
• Read-only review rounds with anchored findings where the Agent rollout is enabled; Generate image as a contextual tool that saves files to Assets.
• Task and mission code names identify their work context separately from the title and assigned agent.
• Tasks, rounds, receipts, mission grouping, dependencies, Board, Roadmap, Triage, and Command center.
• Living Project Context, mission PRDs, task specs, reviewed PRD-to-task proposals, and stakeholder project updates.

Build and review

• Claude Code, Codex, Cursor, GitHub Copilot, OpenCode, Aider, and Mistral Vibe setup/detection.
• Anthropic, OpenAI, Google AI, Mistral, Qwen, MiniMax, z.ai, DeepSeek, Kimi, and OpenRouter BYO provider keys through compatible local engines.
• Paid, project-grounded microphone input that stages a live transcript in the active composer without submitting it automatically.
• Isolated task worktrees, parallel ownership, live run details, plan progress, needs-input/approval cards, steer/stop/resume where supported, exact Changes, Gates, browser verification, receipts, and Accept/Discard.
• Task-only Preview, terminal, contextual single-file workbench, exact-worktree Open in IDE, and pull-request creation.
• On supported Mac builds, consent-controlled connected browser and computer use, with visible activity and machine-local evidence. See Desktop, web, and mobile.

Design and spatial work

• Design canvas with direct manipulation, frames, components, variables, pages, immutable Versions, collaboration, comments, and task-attributed provenance.
• Safe selection-scoped generated Design mutation, explicit Design-to-code reconciliation, and project-bound Figma frame import.
• One project design system with repo extraction, catalog/default sources, code scaffold/write-back, design pack, drift conform, and code-backed component bindings.
• Project Map repository intelligence and Whiteboard with nine editable structured formats.

Context and continuity

• Uploads, saved Assets, integrations, semantic context health, cited project/task Ask, and saved Chats.
• Temporal project memory, immutable Context Pack v2, audit evidence, Forget/redaction, and local/cloud parity.
• Stable task and mission Markdown filenames for exact cross-task references.
• Project/task rules with locked inheritance and separate deterministic Gates.
• Progressive artifacts, generated images, uploads, Assets, versions, provenance, and quotas.

Teams and access

• Project roles, invitations, presence, cursors, follow mode, comments, notifications, and same-user RemoteBridge.
• Exact-target Share for review with View or Comment permission and no Studio/machine authority.
• Project-scoped integrations, external-agent MCP keys, and short-lived outbound run gateways.
• Slack and public-link intake, Slack needs-input notifications, and previewed Linear import.

Local, cloud, and delivery

• The studio requires an account and an internet connection. Local projects use the same studio with a folder on your machine: source files and engine execution stay on that machine, while project metadata, tasks, settings and Design state use hosted services. Local does not mean fully offline or that all project data stays on the device.
• Free includes unlimited local projects and one active collaborative cloud project. Project collaboration and publishing a saved target for review are explicit actions. Project membership and review links do not grant access to another person’s machine. Opening Design does not automatically synchronize the source folder.
• Responsive web/mobile cloud client; hardened, signed, notarized, auto-updating Mac app.
• Separate interface and project output languages across 13 locale targets.
• Free local/cloud allowance, explicit managed-credit choices, quotas, atomic reservations, and budget safeguards.

Availability

An engine being detected does not mean every engine supports every control. Agent review and Community distribution have separate rollout gates; a template is not certified merely because it is listed. On desktop, App settings → Connections → Extensions manages supported native engine extensions. Availability follows the installed engine and the Extensions feature switch. A listed connection is not proof that its account sign-in or tools have passed live acceptance.

Use the navigation for operating details. The product intentionally has exactly two making modes—Build and Design—and no separate Conductor, Code, role, or duplicate planning mode.