Working in Studio

Select a workspace and project before editing. Studio provides a canvas and source views of the project, alongside execution history and project resources.

Use Studio in your browser or install the desktop app to work with projects on your computer.

The left rail contains workspace-wide tools such as Tasks, Otto, Chat, Design Docs, Data Tables, Nodes, Variables, Community, and Marketplace. Opening a project adds a second navigation level for that project's source, workflows, runtime information, and attached resources. See Workspace tools and the complete Project tab reference.

Edit a workflow

1. Open a workflow and select Start to inspect its invocation parameters.
2. Add a built-in node from the palette, or choose an installed plugin node.
3. Connect an output to a compatible input. Use the Inspector to review the input and output schemas and set fixed values or expressions.
4. Save the workflow before expecting another caller or scheduled execution to use your changes.
5. Run it with an input object and open Executions to inspect the outcome.

Every workflow has a Start boundary, including workflows projected from source. Its Types tab describes parameters; its Endpoint tab provides a copyable HTTP execution URL. See Inputs, execution, and triggers.

Work with source

The Code tab edits project source. Compile after source changes to refresh code-owned signatures and check the resulting workflow structure. Source-backed workflows preserve the relationship to their functions; edit source-owned logic through the supported source editors.

The Documentation tab edits ordinary project text files such as Markdown, JSON, and YAML. These files belong to your project. Saving a project document does not publish it to the public Playbook or community catalog.

Test and debug

Use Evaluations to discover supported test files and run available cases or files with the project's installed runner. Jest, Vitest, and Playwright files with direct runner imports can be projected into source-backed test workflows. Fixture and source edits use revision checks; reload if another edit has changed the underlying file.

For a failed execution, inspect the first failing node, its input, and its error. A downstream skipped node often points to an upstream failure. The workflow status can be ok, error, or partial; inspect the status as well as any outputs.

Manage project resources

• Data tables persist structured runtime data in global or project scope and can be attached to projects.
• Variables hold configuration and secrets. They are separate from source-backed Values.
• Tasks plans workspace work and links it to projects, workflows, pull requests, and Chat without changing project source.
• Otto runs an assistant session against explicitly selected projects; Chat is the human collaboration surface.
• Marketplace installs reusable workflow plugins into the workspace library; the project's Plugins tab controls which of those plugins the project uses.

Project settings in Studio edit project metadata. The separate human-authored octonode.yml settings file currently has loader, schema, and read-only CLI support; its appearance and view declarations do not yet change Studio rendering. See Configuration reference.