Project tab reference
Learn what every Studio project tab reads, changes, persists, and shares.
Opening a project adds a horizontally scrollable tab bar. Every tab stays inside the selected project, but some views project repository-wide data or attach workspace-owned resources. A project that still needs installation, is unavailable, or uses a read-only legacy runtime may lock editing tabs and keep Details available.
Project tabs at a glance
| Tab | What it does | Authority |
|---|---|---|
| Details | Shows project location, workflow count, local/hosted status, repository registration, installation or sync actions, and lifecycle controls. | Project registry and files |
| Settings | Edits name, version, description, API keys, resource shortcuts, and archive/delete controls. | Project metadata |
| Workflows | Lists workflows; opens the canvas, node Inspector, code panels, evaluations, executions, and run controls. | Source plus project workflow configuration |
| Tests | Discovers supported test files, runs cases, and opens editable source locations. | Repository test files and runner |
| Architecture | Maps the owning repository, projects, dependencies, resources, frontend previews, pull-request implementation, and repository-scoped assistant. | Registered repository projection |
| Assistant | Opens an Otto session already scoped to this project. | Private/shared Otto session |
| Design docs | Creates collaborative decision documents restricted to this project. | Workspace collaboration storage |
| Monitoring | Shows the fixed production-health view from persisted execution data. | Run telemetry |
| Analytics | Creates private custom dashboards over approved run-stat sources. | Per-user project dashboard definitions plus run telemetry |
| Types | Finds and edits source interface, type, and enum declarations by flow, file, or project scope. | TypeScript source |
| Values | Finds and edits source const declarations for non-secret fixed values. | TypeScript source |
| Classes & services | Inspects and edits classes, state, methods, inheritance, services, lifecycle, and exposed workflow methods. | TypeScript source |
| Data tables | Creates project tables and attaches reusable workspace tables. | Durable table storage plus project attachment |
| Nodes | Browses nodes available in the selected project. | Built-in, source, and attached-plugin node catalogs |
| Plugins | Attaches workspace plugins or project-local npm plugins for this project. | Project manifest, lockfile, and attachments |
| Variables | Creates project configuration and attaches reusable workspace secrets by name. | Protected configuration plus project attachment |
| Code | Edits project files, manages worktrees and terminals, and compiles source changes. | Repository checkout and project store |
| Documentation | Creates and edits project Markdown, JSON, YAML, and text files with source/preview modes. | Project files |
Details
Use Details to identify where the project comes from before changing it. Hosted projects show their repository root; local projects show their path. Cloud copies that are not installed expose an install action. Repository registration connects the project to the Architecture that owns GitHub and repository-wide implementation state. Archive keeps files; Trash is recoverable for 30 days; permanent deletion requires an explicit confirmation and follows each shared resource's own retention.
Settings
Settings changes the project's stable metadata. Renaming does not change its project ID, so links and scoped keys retain their binding. API access creates project-scoped credentials when the role allows it. Resource shortcuts open Variables, Data tables, Plugins, and Code; they do not duplicate those resources inside settings.
Workflows
Select a workflow to open its graph. Workflow edits topology and node configuration, Evaluations runs supported test cases, and Executions shows run history and node-level results. The Inspector edits fixed inputs and expressions, opens source, disables or duplicates nodes, and can replay a node when a completed record exists. Save topology and source changes before another caller can rely on them.
Tests
Tests discovers Jest, Vitest, and Playwright files with supported runner imports. Run a file or case, inspect its projected graph, and open a failing location in Code. Test discovery does not turn arbitrary files into workflows, and editing uses the same revision protection as other source.
Architecture
Architecture belongs to the registered repository, not independently to each nested project. Its Map inventories projects, manifests, source, workflows, nodes, shared plugins, variables, data tables, and declared dependencies. Frontend discovers runnable previews and existing Storybook stories. Implementation projects GitHub pull-request changes onto affected projects and workflows. Assistant opens Otto across contained projects. The graph is derived and cannot be edited as a second copy of the repository.
Assistant
The project Assistant tab scopes Otto to this project at session creation. The session transcript and run state remain Otto data, not project source. Tool-produced project changes still use project permissions and revision checks.
Design docs
Project Design Docs are collaborative revisions linked to this project. They support review comments and optional revocable sharing, but are not repository files. Use Documentation for files that should travel with the repository. Saving either surface does not publish it to Community or the public Playbook.
Monitoring
Monitoring is the fixed operational dashboard for a selected time window. It reports execution volume, success and failure, duration percentiles, workflow distribution, and recent operational signals from stored run data. It does not execute workflows or create another telemetry store.
Analytics
Analytics builds a private per-user dashboard over the same run statistics as Monitoring. Create a dashboard, choose approved stat, area, bar, or pie sources, and reorder its widgets. It does not run arbitrary SQL or join data tables; use the Data Tables SQL editor for table queries.
Types
Types are compile-time source declarations. Filter them by flow, file, project scope, kind, use, or path; create, edit, move, export, or delete them with revision validation. Compatible workflow input types become Studio forms. Types do not persist runtime values.
Values
Values are source const declarations. Literal text, numbers, booleans, lists, and objects can use
the structured editor; advanced expressions stay in Code mode. Flow-local values remain inside a
flow, file values remain private to a file, and project values are exported for imports. Values are
not secrets or mutable durable data; use Variables or Data tables.
Classes & services
This tab presents TypeScript classes as Construction, State, and Capabilities. Plain classes remain
source structure. Explicit instances or methods exposed through defineService can become workflows.
Service lifecycle controls whether memory lasts for one invocation, one workflow run, or one worker;
none of those lifetimes makes state durable. Store durable state in a data table.
Data tables
Create and edit project-owned tables inline, then attach global workspace tables for reuse. A project resource marked as owned cannot be detached from its own project; a global attachment can. See Data tables for storage modes, SQL, relationships, saved views, and API access.
Nodes
Nodes lists definitions available to the project from native capabilities, project source, and attached plugins. A catalog entry describes a node contract; a node placed on a workflow canvas is a configured workflow instance. Editing source-backed behavior still changes project source.
Plugins
Attach a plugin already installed in the workspace Marketplace, or add a project-local npm plugin. Attachment can update the project manifest, dependency installation, and lockfile. Wait for a successful install before using its nodes, and configure required Variables separately. Detaching a workspace plugin from one project does not uninstall it from the workspace library.
Variables
Create project-only variables and attach global variables from the active workspace. The project sees only its own and attached names. Variable values remain protected configuration and are omitted from exports. See Variables and secrets.
Code
Code edits the selected checkout's project files and exposes compile, problems, Git worktrees, and project-scoped terminals. Compile refreshes source-owned signatures and validates workflows; it does not rewrite arbitrary implementation logic. A terminal can be a separate scratch container, so use the project APIs or editor for durable project changes and verify the saved revision afterward.
Documentation
Documentation manages ordinary project files in supported text formats. Source, preview, and split modes share one revision-checked draft. If the saved file changed, compare or download your draft before explicitly replacing it. These files travel with the project and can be committed to Git; they are not Design Docs and are never automatically published.