Agents are the stones. You lay the street.

Spin up agents with roles and scoped permissions, put them to work alongside your people, and keep the gate: decide what each agent may do on its own and what it must ask you for, and see what it spends.

Porta Maggiore · Piranesi, 1775

How it works

It asks. You decide. It's on the record.

  1. 01Milo reaches a tool set to Ask first.
  2. 02The request waits for a person.
  3. 03You allow it once, always, or deny it.
  4. 04The action and the decision land in Activity.

Example workspace · names and figures are illustrative

MiloOperations
DanaClean up the duplicate leads before Friday's review.
MiloFound 3 duplicates in Leads. Merging their details into the originals, then removing the copies.
Correct recordsDone
An allow setting covers this — no approval was needed.
Delete recordsWaiting
Lead #2841 · duplicate of #2207
Needs a person’s approval to run.
Allow onceAllow alwaysDeny

Activity, Today

08:52Looked through your records
09:13Corrected a record
09:14Removed a record
Credits this cycle: 1,284

Supervision

Every agent answers to someone.

Roles

A job, not a chatbot

Each agent gets a role, the instructions it goes by, and only the tools you give it.

Policy

Allow · Ask first · Deny

Set per tool. Routine work runs on its own; anything you want to see first waits for you.

Approvals

The gate waits for you

When an agent needs a yes, you see what it wants to do before it runs.

Activity

Everything on the record

Each agent's Activity holds what it did, what it asked for, and how it was decided.

Halt

Stop means stop

Halt an agent and it stops working until someone resumes it.

Credits

Spend in plain sight

Usage is metered in credits and shown on the workspace's Usage page.

The record

The street remembers.

Activity adds up over time into a history of what each agent did, and how each request was decided.

Lay the first stone.