You approve every change
Operator reads your record, proposes an exact set of changes, applies only what you approve and reads the record back to check it worked.
Send three W-8BEN reminders
Reading 28 LPs, 31 documents, 6 tasks
- Investigate
- Propose
- Approve
- Apply
- Verify
$operator watch 7c1e04
See every job’s next step
Every job shows what it’s doing, who it’s waiting on and the one thing to do next, with the detail a click away.
Steer a running job
Change a job’s course while it runs, let it pick up where it stopped, or keep its steps for next quarter.
CLI & MCP
Run jobs from your terminal
Run, follow, steer and stop jobs from your terminal or your agent, and sign off in the app with the exact change in front of you.
# Start a job and follow it
$operator run "Chase the LPs missing a W-8BEN for Fund II" --watch
# Everything waiting on you
$operator jobs --status waiting
# State, changes and the approval link
$operator job 7c1e04
# Follow it until it needs you or finishes
$operator watch 7c1e04
# Change course mid-job
$operator steer 7c1e04 "Skip Halden Holdings"
# Open a new 15-minute window
$operator continue 9b3d22
# Stop it; nothing unapproved happens
$operator cancel 7c1e04
- runStart a job
- jobs_listWhat’s running and what needs you
- job_showState, changes and the approval link
- job_steerAdd an instruction
- job_continueOpen a new window
- job_cancelStop a job
Install with npx @allocator-one/operator · add it to any MCP client with operator mcp
What an approval means
An approval is a signature on one exact set of changes, checked again before each change is made.
- One exact set of changes
- An approval is tied to the job, its plan version, every target and every value. It expires, and it never stretches to cover anything else.
- Every change made at most once
- Every approved change is made at most once and leaves a receipt, so a retry or a restart can’t send the same email twice.
- Jobs report partial outcomes as they are
- If some changes land and others don’t, or an outcome can’t be confirmed, the job says exactly that instead of calling it done.
- Rights checked at every step
- Operator re-checks the access of the person it works for before reading, before proposing and before applying. Lose access, and the job stops.
- Approve the exact message
- Before an email or invitation goes out you approve the exact message, recipients and attachments. Change one word and it needs approving again.
- You choose who sees notes
- Notes and files you give a job are kept private, shared with your organization, or used for that job only. You choose, and can see which.
More on Operator
Four views of Operator
Each page covers one part of how Operator works.
Plans
Plans across Operator and your team
Chains of work that run for days or weeks, across Operator and your team, with the waits between them.
See plansTools
402 tools across your fund
Operator can use every tool on your record, from CRM search to capital calls.
See the toolsCLI & MCP
Operator in your terminal, CI or agent
Run Operator from your shell, your scripts and your CI, or hand it to your own agent over MCP.
See the CLI
Common questions
Approval is where you check the exact change, so it happens in the app with the full change on screen. The CLI and your agent start and follow the work, and hand you the link the moment it needs you.
Not yet. Releasing a plan lets Operator start its steps, but every change a step wants to make still waits for its own approval.
Operator checks each target again before it applies a change. If the record has moved on in a way the approval didn’t cover, it stops and asks instead of overwriting.
The person the job works for, or someone they’ve delegated to. A delegate approves with the job still running on the original person’s rights, never their own.
A new window draws on the same job budget, and the job shows what’s been spent so far before you press it. When the budget runs out, Operator stops starting work.
Yes, at any time, from the app, the CLI or your agent. Changes already approved and applied stay as they are; nothing unapproved happens after you stop it.
See each change first
Operator proposes an exact set of changes and applies only what you approve.