Listing and inspecting Agents
--json to any command for machine-readable output.
Creating, updating, and deleting Agents
Duplicating an Agent
Copy an existing Agent into a new one namedCopy of <name>. Everything except its Memory is carried over — Connections, Queue, Skills and Files, Logins and Secrets, plugins, and the AOP. Use the --no-* flags to leave parts behind.
To also copy an Agent’s Memory, duplicate it from the Duvo app — Memory isn’t copied through the CLI.
Starting Runs automatically
Agents can start Runs on their own — on a schedule, when an external event fires, or when a Case lands on a Queue. These live on their own page: see Scheduling and Triggers forduvo agents schedules, duvo agents triggers, and duvo agents case-triggers.
Organizing with folders
Group Agents into folders for easier navigation.Revisions
A Revision is a versioned Setup snapshot of an Agent. Each time you publish changes, a new Revision is created. Most workflows don’t need to manage Revisions directly — Runs always use the latest Revision automatically. Use these commands when you need to roll back, compare versions, or update a specific Revision in place.POST /v2/agents/:agent_id/code-step-files and returns sha256, sizeBytes, and bucket. Each file may contain up to 128 KiB. Uploading does not change a Revision: put the digest and size in the file’s entry in config.source.bundle, use the returned bucket for the bundle, and save the full config with duvo revisions update <revision-id> --config-file config.json on a draft. Re-run the draft to check it before promoting it, and promote only after the user explicitly approves going live.
To change only the AOP, keep it in a Markdown file and pass --aop-file. The CLI loads the Revision’s Setup, replaces the AOP, and leaves everything else as it was. update works on a draft Revision; to change a live one, create a new Revision from it:
Memory
When an Agent has agentic memory enabled, it persists notes across Runs as memory files. Use these read-only commands to see what an Agent has remembered.duvo agents update <agent-id> --enable-agentic-memory / --disable-agentic-memory.
Evaluation rubrics
Every Run is scored against evaluation rubrics: the platform default rubrics plus up to five custom, Agent-specific rubrics per Revision. Custom rubrics are Pass/Fail checks written as a short title and a Pass condition. Use these commands to read and manage the custom set.--json to any command for machine-readable output. These default to the Agent’s live Revision; pass --build <build-id> to read or edit the set on a specific Revision.