Operator
← Operator

The platform

One engine. Every surface.

Operator is a single agent engine, written once and run everywhere — the terminal, a native iOS app, and the web. It drives a real tool loop over your files, git, shell, the web, and your MCP hub, holds your whole codebase in context, and records everything it does.

The engine

A real agent loop, not autocomplete.

01

Whole-codebase context

Operator reasons across your repository, not a snippet — planning, editing, and testing with the full picture in view.

02

Tool registry

A governed catalogue of tools the model can call: files, git, shell, web, and your own via MCP. Tiered per account.

03

Context management

Long sessions compact safely without losing the thread, so work continues across hours, not just a single prompt.

04

Permissions built in

Every irreversible or outward-facing action is gated behind explicit approval — the loop pauses for a human.

Tools & connectors

It acts on your systems — with your rules.

Operator does the work through tools, not suggestions: it reads and writes files, runs your build and tests, commits to git, searches the web, and calls your internal systems through the Model Context Protocol.

50,000+
MCP skills via the remote hub
Files · git · shell
The core developer loop
Your systems
Internal tools via MCP

Approvals & audit

Approve

Human in the loop

Destructive or outward-facing steps wait for sign-off. Approval is per-action and never carries across contexts.

Record

Tamper-evident trail

Every action is written to an append-only audit chain — reviewable, and impossible to quietly rewrite.

Scope

Tiered access

Admin, member, and read-only tiers; scoped API keys per project, revocable instantly.

One engine · every surface

Terminal

The CLI

The full loop in your shell. operator installs once and signs in once; the same account follows you.

Mobile

Native iOS

Drive and observe a live session from your phone — diffs, tool steps, approvals, documents, and media.

Web

Browser & remote

Run in the browser or attach to a running session on another device, and hand it off without losing state.

How it works

01

Connect

Install the CLI or open a surface, sign in once, and point Operator at your repo and your tools.

02

Instruct

Describe the outcome. Operator plans, edits, runs, and tests — asking before anything irreversible.

03

Review

Read the diff, the tool trace, and the audit trail; approve, and ship.

See it on your codebase.

Enterprise & government · by approval

Request access → Solutions