Public beta — service businesses & agencies

Meet your first operator.

A private AI operator with its own computer, its own memory, and one standing rule: it asks for your initials before it spends a cent or sends a word.

ExampleDay book — Clawd, operatorTUE 07:00on duty
Outcome received on web chat: “Chase the three proposals that went quiet.”
Read company instructions and memory — pricing rules, tone, the three accounts.
Cell resumed. Drafted three follow-ups from the proposal files, one per account.3 drafts
Sending external email is a boundary: credits reserved, drafts filed, and the slip below waits for initials.0.42 cr held

Send 3 follow-up emails via Gmail

To the named contacts on each quiet proposal. Drafts attached as evidence.

CELL running for this runLEDGER 0.42 cr on hold

A worked example, stamped as one. Nothing on this page claims a live connection it does not have.

The file

What your operator arrives with.

Not a chat window — a worker with equipment, records, and rules. Everything in this file is a surface you can open in the workspace.

Their own computer

An isolated Cell that keeps files and browser state between runs, resumes to work, and pauses when idle.

Paused when idle
Company memory

Instructions and durable facts you can read, edit, and delete — injected before every run.

Yours to edit
Specialists

One operator owns the outcome and hands bounded tasks to narrow specialists you define.

Delegation
A paper trail

Every run keeps durable steps, artifacts, and evidence you can read back later.

On the record

Certificates

Skills you read before you install.

Every skill is a manifest: what it does, what it needs, what it may do, and what it will never do. 7 ship with the beta — a starter catalogue, not a marketplace counter.

Read all the certificates

SkillWhat it doesBoundary
Lead QualifierAsk smart questions, assess fit, and route to the right owner.sends with approval
Meeting BookerFind time, book, and confirm across calendars.sends with approval
Inbox TriageSort, label, and draft replies that match your voice.drafts only
Proposal DrafterCreate proposals from your templates and your data.drafts only
Invoice FollowerNudge politely and escalate when needed.sends with approval
Knowledge FinderSearch your documents and surface the right answer.read only

Authorizations

Connected means the provider confirmed it.

Your operator works through the tools you already use, inside the scopes you grant. A connector only says “connected” once the provider confirms it — never because a redirect finished.

See all connectors

1Choose2Authorize3Select scope4Confirm5Connected

Reaching them

Every channel says where it truly stands.

Start a conversation where you already work. No channel below claims to be live unless it is.

ChannelWhat it is todayState
WebThe in-app operator chat. Always available to every member of the workspace.Live
WhatsAppOfficial Meta WhatsApp Cloud API. During beta the number is registered with you by the fist.chat team.Live after setup
SlackDM or mention the operator in a channel. The Slack connector authorizes today; the inbound message route is not built yet.Staged
TelegramDirect chat with the operator. Running on the owner pilot only; per-company bot provisioning is not built yet.Staged
Microsoft TeamsNot available in the beta. No Teams app is published and no route exists.Not available
iMessageRunning on the owner pilot bridge only. There is no multi-tenant iMessage route, so it is unavailable to beta workspaces.Not available

The ledger

Every credit, accounted for.

Beta workspaces run on managed model credits. A run reserves before it starts, settles what it used, and releases the rest — with an itemized receipt separating model tokens, Cell compute, and tool calls.

How credits work

ExampleOne run, one receipt
09:00Reserve. Credits are held before the run starts, so it can never overspend the workspace.Held
09:03Settle. Metered usage — model tokens, Cell compute, tool calls — is converted to spend, itemized.Settled
09:03Release. Whatever the run did not use goes straight back to the balance.Released

RECEIPT — held, settled, released: three lines, every run.

The background check

Private by company. Controlled by people.

Data privacy

Your records stay scoped to your company. Provider tokens never enter Firestore or a prompt.

In code
People and roles

Invite teammates with owner, admin, operator, or viewer capabilities.

In code
Approvals

Sends, publishing, deletion, purchases, and permission changes wait for a person.

Waits for you
Activity log

Runs carry durable steps, artifacts, and evidence you can read back.

In code

Read the security page