Skip to main content
This page covers common agent lifecycle operations in the dashboard, with the CLI, and over the API. CLI examples assume you have run omnara login and omnara config select; API examples use a bearer token:

Launch an agent

Create an agent from a config, or from a profile if you want the launch tied to a named template.
Full schema and playground: Create agent.

Find agents

The project’s Agents page lists active agents; click one to open its conversation. omnara agents list and the API return active agents newest first; fetch one by ID with omnara agents get {agent-id}. Archived agents are omitted from the list but remain retrievable by ID.
For full schemas and playground see: List agents and Get agent.

Stop current work

Stopping cancels the agent’s current turn, pending tool calls, and open interactions. The agent and its conversation remain available; the next input starts a new turn.
The response includes affected: true when work was canceled. affected: false means the agent was already idle, so the request is safe to repeat.
Full schema and playground: Cancel agent.

Archive an agent

Archiving retires an agent. It stops current work, drops queued inputs, releases machine bindings, and deletes pooled machines created for the agent. The agent leaves active listings, but its event history remains available by ID. Machines you connected yourself, configs, and profiles are not deleted.
The response returns the agent with state: "archived". Repeating the request is safe.
Full schema and playground: Archive agent.
There is no unarchive. Launch a new agent when you need to continue with fresh work.

Next

Agent configuration

Define an agent’s model, tools, permissions, and machines

Sending input

Send messages and change direction while an agent works