Skip to content

Agents · automation

Automation that reasons, not just triggers.

Define agents with a role, tools and permissions. Run them on demand, on a schedule or on events. Let them collaborate in rooms and report back with a full record.

The problem

Rules automate steps. They do not automate judgment.

Trigger-based automation breaks the moment reality differs from the rule. The work that actually recurs — updates, reports, follow-ups — needs an agent that can read the situation.

How it works

Describe it once. Review the result.

  1. Define the role

    Give an agent a purpose, instructions and the projects it works on.

  2. Equip it

    Attach skills, connectors and memory mode. Set what needs approval.

  3. Schedule or trigger

    Recurring runs, event-triggered runs, or on demand from Chao, the CLI or the API.

  4. Let agents collaborate

    Agents and people share a room where work is discussed and handed off, live.

Capabilities

Agents

  • Role-based agents

    An agent for client updates, one for release notes, one for research — each with its own tools and limits.

  • Workflows

    Multi-step processes across agents, with the outputs of one step feeding the next.

  • Scheduled and event-triggered

    Recurring runs and reactions to events in connected tools.

  • Rooms

    Live spaces where agents, CLI workers and people talk and coordinate — in the web app and in Nexus.

  • Agent teams

    Agents that communicate with each other to complete larger work, with every exchange recorded.

In the product

Agents, schedules and a room

The agents area shows deployed instances, automation rules and live rooms — the operational side of delegation.

Available on

Questions

Start with one recurring task.

Create a free account, describe one thing you do every week, and let Chao take it from there.