Skip to content

Surface — Chat

Delegate work in a browser. Real changes, held until you approve them.

A browser agent with your approved tools and a workspace. Actions that reach your systems collect for a decision, then run.

Spec
Trigger
You, in conversation
Execution
Managed workspace
Review
Reviewed in seconds to minutes
Gate
Named human · batched

Definition

What it is

A browser agent with tool access, a workspace to build in, and a panel that collects the actions it wants to take.

  • The actions accumulate rather than firing.
  • It reaches C2 and C3 like every other surface — a ticket edit, an outbound message, a deploy — and each one waits in that panel for a named human.
  • What you approve then executes against the real system.

Approval

How approval works

Related actions batch into a single decision.

  • You execute when you are ready — all of them, or some of them — and what you approve takes effect in the system itself.
  • Execution returns to the conversation as an event the agent sees, so it plans from what you actually authorized rather than from what it asked for.

Fit

When you reach for it

Exploratory and compositional work you want to steer while it happens, whether the output is a document, a dataset, or a change to a live system. It is the one surface that assumes no technical proficiency: it asks you to hold a conversation.

In practice

Three ways this gets used.

Engineering

Pull requirements from several sources and assemble a trade study comparing candidate approaches, steering which sources count.

Program management

Build a status deck from the tracker, the wiki, and last month's metrics, iterating on the framing live.

Software development

Interrogate an unfamiliar service — code, runbook, recent incidents — and produce an onboarding brief.

Next

See Chat configured for your tools.

A briefing walks through how a handful of your real tools would register on this surface — the classes they reach, where the gates land, and what stays identical on the other three.