Skip to main content
Cyberwave has three agents. They sit on top of everything else: they build the environment, decide what the robots do, and write the automation, all from a plain-language request. Each one shows you what it intends to do and waits for your approval.

Environment assistant

Builds the world. Describe a scene; it places robots, sensors and objects, and generates assets the catalog doesn’t have.

Control agent

Drives the robots. Describe a task; it plans actions and skills the twin actually supports and runs the one you approve.

Workflow assistant

Automates the work. Describe a recurring job; it drafts or edits the workflow that does it.

​
Which one do I need?

A typical session uses all three in order: build the scene, try the task with the control agent in simulation, then turn it into a workflow.

​
How approval works

  • Plans come first. Every agent returns a plan or a proposal before changing anything.
  • You approve one step at a time. The control agent dispatches a single action only with explicit confirmation. The workflow assistant applies an edit only after Review and apply.
  • Simulation before hardware. Plan and test in simulation, then plan again for the real robot.
  • A person can always take over from the twin’s controller panel. See Ways to control a robot.

​
Where you use them

To give Claude Code, Cursor or any MCP client these abilities, see the MCP server and the Claude skill under Reference.

​
Next steps

Control agent

The most common starting point: plan, approve and run an action.

Control an SO-101 with your voice

Voice in, a plan out, the arm moves.