A project-first Studio that teaches the workflow while you use it.
DynosAI Studio is designed for people managing small local software projects who should not need to understand SQLite, MCP events or internal workflow-state names before they can safely use coding agents.
Project hub first
Studio opens on a neutral project hub unless you explicitly launch it with --project. Returning Home leaves the active project context and keeps it in Recent projects.
Project-scoped workflow
Overview, New change, Work, Approvals and Project checks appear together under the selected project instead of competing with global Studio pages.
Folder browser
Create and Open actions use a contextual in-Studio directory browser. Path fields are read-only, and you can navigate folders or create a new directory without leaving Studio.
Natural-language changes
New change contains only the request. Agent, workspace and model routing are configured once in Project settings and reused automatically.
Visible agent execution
Creating a change starts Codex through app-server or Cursor through ACP without blocking Studio. Work now includes a bounded live activity trace so users can see provider progress without opening raw diagnostics.
Project configuration
Project settings choose Codex or Cursor, Interactive branch versus Isolated worktree, Strict/Balanced/Autonomous execution profiles, optional harness optimizations, and the model routes for the selected agent.
Approvals you can actually review
Specification gates show requirements and acceptance criteria; plan gates show tasks, files and risks; code/merge reviews can expand the resulting diff, validation results, integrity risks and execution-policy evidence.
English and Spanish
English remains the default. Spanish is included and the translation dictionary is designed so more languages can be added without duplicating the UI.
Contextual Fibonacci walkthrough
The tutorial no longer creates or performs the workflow for you. It highlights the exact screen, field and button while you create the greenfield project and complete each step yourself.
Normal Studio path
Home → choose a project → Overview → New change → Work / Approvals → Project settings
Before initialization, only Overview is interactive. Initialization shows progress and sends you to Project checks only when detected checks need approval. Risk internals, diagnostics and the activity stream stay optional.
Learn by doing, not by automation
The Fibonacci walkthrough is contextual. It asks you to create a neutral project, initialize it, enter the Fibonacci request and make the approvals yourself while Studio highlights exactly where to act. Project checks remain available, but the tutorial no longer depends on pre-existing pytest configuration and stays with you through repeated approvals until the work is actually complete.
Consistent controls
Core choices and confirmations use Studio-native controls styled to match the shadcn/ui interaction language used on dynosai.com. Browser-native select and confirm dialogs are not part of the normal Studio flow.