Skip to main content
Drag, drop, and orchestrate Agents, Teams, and Workflows on a live canvas to deploy production-ready agentic systems with AgentOS Studio.

Concepts

How It Works

Studio connects to your running AgentOS instance and uses a Registry to populate available components. Build visually, test interactively, and publish when ready.
  1. Register your components in a Registry
  2. Pass the registry and a database to AgentOS
  3. Open Studio in the control plane to start building

Development Lifecycle

Studio manages the full development lifecycle from building to deploying complex agentic systems with AgentOS components.

1. Build

Create your agent, team, or workflow using the visual builder. Drag components from the Registry, configure properties, and wire everything together.

2. Save Draft

Save your work as a draft version. Drafts are not accessible via the API but can be tested, restored, and published later. You can save multiple draft versions to checkpoint your progress.

3. Test

Once saved, test your draft in the AgentOS Control Plane:
  • Chat Page: Interact with your agent, team, or workflow in real-time
  • View Traces: Inspect tool calls, model responses, and reasoning for each run
  • Debug Mode: Enable verbose logging to troubleshoot issues
Before publishing, test and make sure your agent handles edge cases and unexpected inputs gracefully.

4. Publish

Move from draft to production with one click. Publish the visual blueprint of your agentic system after verification. Manage multiple versions of your system blueprint. Every published version is immediately accessible via a unique API endpoint. Set any version as Current to make it the default for your production API.

5. Manage Versions

Access the full version history for any agent, team, or workflow:
  • Restore: Load any previous version into the editor
  • Set Current: Choose which published version is used by default when running via the API
  • Delete: Remove old versions you no longer need
Use descriptive version labels like v1.2-improved-instructions or before-refactor to make it easy to identify versions later.

Next Steps