The right human oversight forfast moving agentic engineering

Know when and where to step in

Spot agent sessions that need human attention in the feed, review the work quickly, and make the next call without babysitting

app.buildautomaton.com

Feed

Team session activity

7 daysGroup by: creator
Session 1Needs review
Prompt 1
Prompt 2
Samtyping a comment…

I would do this instead:

Session 2
Prompt 1
Prompt 2

Notifications

Needs your attention

Prompt finished

Permission needed

Talk to us

Bring existing compute hosts and agent subscriptions into a managed AI fleet

A bridge connects each host you already use to one shared workspace, so the team can follow, review, and control agent sessions across the fleet.

app.buildautomaton.com
BuildAutomaton

Sessions list

Agent session

Work laptop

Your application
Cursor
CLI bridge

Cloud host 1 on your infrastructure

Your application
Claude Code
CLI bridge

Cloud host 2 on your infrastructure

Your application
Codex
CLI bridge
Terminal
$ npx @buildautomaton/cli@latest
Secure tunnel connected
Secure tunnel
app.buildautomaton.com
Shared workspace

A secure bridge brings each host into your managed AI fleet

Run a CLI bridge on each laptop, workstation, server, or cloud host you want managed from the shared workspace. The agents and dev environment on that host become available to the team.

Work laptopClaude
VPCOpenCode
VPCCursor
Secure tunnels
Shared workspace
One surface, many hosts in parallel

Use the compute hosts and agent subscriptions you already have

Keep using Cursor, Claude Code, Codex, and other agent subscriptions on hosts your team already controls.

Shared workspace

Review
ReviewCommentControl

The shared workspace gives the team visibility and control

Team members can see agent sessions, inspect the work, and take action when the host owner grants permission.

Protect your intellectual property end to end

Sessions, code files, and agent output are encrypted on the CLI bridge before they leave your host. Only browsers with your certificate can decrypt them. End-to-end encryption.

Installed on CLI bridge

Your certificate

CERT 7C:42:BA

Same certificate on both sides

Installed on browser

Your certificate

CERT 7C:42:BA

CLI bridge

$ npx @buildautomaton/cli@latest

Secure tunnel
app.buildautomaton.com
BuildAutomaton

Sessions list

Agent session

Encrypted before it leaves the host

Sessions
Code files
Private data

Keep fast-moving agent work under human oversight.

See when sessions need attention, bring the right people into the work, and review changes in the environment where they run.

Explore the product

Frequently asked questions

What types of agents are supported?
BuildAutomaton uses the Agent Client Protocol (ACP), so it supports any agent that implements ACP—including Cursor, Claude Code, Codex CLI, Kiro, and more. See our Supported agents docs for the full list and compatibility notes.
How do I set up a bridge?
Run the CLI on the machine you want to make accessible. After installing Node.js, run npx @buildautomaton/cli (or install the CLI globally). The bridge stays connected until you stop the CLI. See our Getting started guide for full steps.
What does it cost?
We have a flat subscription fee for BuildAutomaton—see our Pricing page. Your local agents (Cursor, Claude Code, etc.) are priced separately by their providers; you’ll need a subscription for those separately.
How is the local bridge secured?
The bridge requires authentication. Only authenticated users can access the resources that the bridge makes available.