
AI employees
Six roles hold jobs: workflows, living files and wakes. Name one with @presales.
Give it a goal in plain English. It works in a sandbox, tests the result against checks it wrote first, and asks before anything leaves your hands. Ask it how, and it shows you.
Drag the windows. Approve drafts in Jobs and watch Twin earn trust. Everything here is an illustration on demo data.
V1 · Checks first
Your request becomes typed success criteria: a file exists, it contains what you asked for, it opens cleanly, it was delivered.
file_exists · contains · file_valid · delivery_receipt
V1 · Evidence
One check fails. The agent sees the evidence, replans and rewrites the file. It does not report “done”.
closes on evidence, never on the model's word
V1 · Delivered
Every check passes and the file lands on Telegram. That is the only way a goal closes.
Telegram · Discord · Slack · WhatsApp · Signal
V2 · A team
Six AI employees hold jobs: the workflows they run, living files, and wakes. Name one with @presales.
@gtm · @creator · @bdr · @presales · @delivery · @builder
V2 · Wakes
An email, a calendar event, a webhook, a changed page or CRM deal starts the right employee.
one run per job at a time; the next wake waits its turn
V2 · Held
The reply is drafted and held. So is the code change: it can only leave as a draft pull request.
approve in Telegram or on the Jobs page
V2 · Approved
Approve, edit, skip with a note, or let it lapse after 24 hours. What is still held stays held.
receipt ap_3f2a91 · logged on the job's run
V3 · Knows you
Positions with dated evidence, in the domains you granted standing for. Nothing outside them.
CHARTER.md · deny by default
V3 · Earned
Only for that action class, only while you are away, and only inside your charter.
earned delegation · live trial
V3 · Acts
Your block rules, the earned delegation and your absence all pass. It answers and logs a receipt for the digest.
1 block rules · 2 earned · 3 you are away
V3 · Revoked
Any edit or rejection revokes the delegation at once. The count starts again from zero.
re-earned only by a fresh streak
Replies and sends go through the same order: your block rules first, then earned delegation while you are away, otherwise it asks. Change a choice and five incoming actions re-route.
Earned is never a switch: five clean approvals earn it, and one edit or skip takes it back. These choices are saved in your own AUTHORITY.md — the table and the file are the same file.
Earned, and you are away. A receipt is logged.
Drafted and waiting for approval.
Stopped by your rule. Always wins.
It does the work where the work is, and reports where you already are.
A Docker container with Python, Node and Bash. Scripts, files and office documents are made here.
A real browser with a live view. If a site throws a CAPTCHA, it pauses and hands it to you.
Telegram, Discord, Slack, WhatsApp and Signal for goals, approvals and finished files.
A companion app on a machine you pair, sharing only the folders you choose. It takes turns with you.
◐ live trialFiles you can download, skills it reuses, memory it can search.
PowerPoint, Excel, Word, PDF and HTML reports, generated, tracked in one place, ready to download.
A solved task becomes a reusable skill. Import Agent Skills, or teach a browser task by doing it once.
Episodic and semantic memory with search, so the second run starts with what the first one learned.
Recordings of it working: two of V1, one of V2.
The real screens, on demo data.

Six roles hold jobs: workflows, living files and wakes. Name one with @presales.

36 ready-made procedures. Start from a pattern, import JSON, or generate one.

Evidence about you inside a charter you own. Autonomy earned per action class.

Browser sessions, folders, desktop control, payments and security testing: each a switch.

Ctrl/⌘ + K goes to any view, opens a chat command, jumps to a recent chat or starts a new one. Runs that need room open as windows you can drag and fold away. Light, dark, or follow your system.
The more it can do, the more the controls matter.
Persistent browser sessions, local folder access, desktop control, payments and security testing each have their own switch, labelled by risk.
Outward actions wait for approval. A message that times out records nothing: silence is never consent.
Every tool call, file write and approval is logged, with per-user usage and cost.
In a team, each member’s files, memory, commands and browser sessions are kept apart at the data, event and identity layers.
Admins see what a twin did (actions, receipts, a freeze switch), never what it knows about its owner.

Counted from the repository, not typed by hand.
It is shared by invitation while the newest parts are watched in live use. Tell us what you would run on it and we will reach out.
Already invited? Sign in. Looking for the guides? Read the docs.