Put agents to work on your systems.
Use a packaged agent, bring one you already have or build your own. oz0 gives the work a place to run, with tools, rules and a history.
Choose your starting point
The words we use
You give an agent a task. oz0 tracks its execution as a job. The agent calls tools; a node runs the work. Plugins package the components you install.
- Agent
- Instructions, a model and permitted tools configured to do a task.
- Model
- The AI an agent uses to interpret information and choose or generate its next response.
- Runtime (harness)
- Software that manages an agent’s context and model/tool/result loop. oz0 provides a default runtime.
- Job
- One tracked execution of a task, with input, progress and a result.
- Tool
- Code or a service that provides actions an agent can call.
- Tool action
- One operation, such as reading logs. A tool call requests that action with specific arguments.
- Skill
- Reusable instructions for a procedure an agent can follow.
- Plugin
- A versioned package you install. It can provide agents, skills, tools or checks, or group other plugins.
- Node
- A machine running the node software, where agent jobs and tools run.
- Server
- The orchestrator-zero binary, also called oz0. By default one process runs management, edge and embedded Temporal. It can share a machine with a node.
- Management
- The server role for the console, administration and cluster configuration. Its command-line role name is manager.
- Edge
- The server role that serves runtime APIs, the model gateway and node connections. It can run in the same process as management or separately.
Ready for the details?
Read tutorials, configuration reference and detailed limits in the public Docs preview. Software and source access are coming soon.
Open the developer documentation