A teammate that stops before it sends.

This is the whole app

The sidebar is the roster. A room like Monday is a group chat where you give the week to more than one Bot at once: Inbox Manager sorts, Expense Manager closes receipts, Chief of Staff names the two decisions that are actually yours. Nothing goes out without you.

The cards look like a team that already ran. Chief of Staff stayed quiet if nothing changed. Inbox Manager left four reply drafts and sent none of them. When a send comes up, the Bot stops: not yet, or send.

What you will have by the end

Two things. Not a fleet, not a workflow builder.

1. 1

   A Bot doing a job you already do

   One Bot, one job, and a description you wrote yourself.

2. 2

   A rule about when it has to ask

   If it is about to send, publish, buy, delete, or sign, it stops. Everything up to that point it does on its own.

Pick one job

Start with a job someone in the room already owns. The three that teach the pattern:

Five words you will see in the app

That is the whole vocabulary. Models, context windows, and sandboxes never come up.

1. 1. Bot

   A teammate with a name, its own memory, its own computer, and its own tools.

   Example: Chief of Staff

2. 2. Chat

   Where you talk to one Bot, or to a group of them.

   Example: Message Chief of Staff

3. 3. Prompt

   An instruction. Use it once, save it as a skill, or schedule it as a routine.

   Example: Every weekday at 8:00

4. 4. Tool

   How a Bot reaches software: a plugin, the browser, the shell, or its computer.

   Example: Gmail · Slack · Chrome

5. 5. Artifact

   What the Bot leaves behind: a document, a draft, a sheet, a change to code.

   Example: weekly-summary.md

Create a Chief of Staff and one specialist

You only talk to one Bot. Chief of Staff routes work and reports back. The specialist is the job the room picked — Inbox, Expense, or Sales Outbound. The description field is enough to create it. Plugins and the approval rule come next.

You are my Chief of Staff. Watch my calendar, Slack, and inbox.

Stay quiet if nothing changed. When something needs me, say what is done, what is blocked, and the one decision only I can make.

Never, without asking: send, publish, buy, delete, or sign.

Plugins are how a Bot gets into your apps

A plugin is a connection to one app: Gmail, Slack, your calendar, your CRM. Add it once for the account, then tell each Bot which ones to use. Every Bot can still reach all of them.

Your own tools go here too. Anything the team builds, or an MCP server, sits next to the public ones. Open Settings → Plugins in the app. Featured connectors include Gmail, Google Calendar, Google Drive, and Slack. Type @ in chat to attach a connector, and / for a saved skill.

This directory lists bots by the tools they work with. Browse integrations or pick the tools you already use.

Set what it has to ask before doing

Set once, in Settings. Require approval for the actions that leave the building. Always allow the ones that only read or draft. When two rules collide, require approval wins.

You are not done setting up until you have watched the Bot stop and ask you once. Draft an email, let it reach Send, and confirm the conversation shows it waiting. Official detail: Approvals, security, and privacy.

When a login comes up, you type the password

You take over its screen, type the password or the code, and hand it back. Nothing you typed ends up in the chat.

1. 1. Glance

   A small icon in the title bar turns purple while the Bot's computer is busy.

2. 2. Look

   Open a side panel and watch the screen without leaving the chat.

3. 3. Sit down

   Open the computer full screen, take control, do the sign-in, hand it back.

Write the first task in five parts

Write all five before you press enter. The Bot does exactly the job you described, so say where it should stop as carefully as what it should do.

1. 1. Outcome

   What should be finished when the Bot stops?

2. 2. Sources

   Which apps, websites, files, or conversations matter?

3. 3. Constraints

   What must the Bot avoid, or ask before doing?

4. 4. Deliverable

   What should it hand back, and in what shape?

5. 5. Review point

   Where does it stop and wait for you?

The first result is something you can check, not something already done. Inbox or Sales hands you a list of drafts — nothing sent. Expense hands you a sorted list of receipts — nothing paid.

Outcome: My inbox is sorted into Needs me today, Waiting on others, Newsletters, and Everything else. Threads where I am blocking someone are at the top.

Sources: Gmail, and the Slack channels #ops and #leadership for context on who is waiting.

Constraints: Do not send, archive, or delete anything. Do not reply to anyone outside the company.

Deliverable: A short list in this chat — each urgent thread, one line on why, and a draft reply saved in my Drafts folder.

Review point: Stop after the drafts are saved. I will read them and send the ones I agree with.

Outcome: Last week's receipts are logged, categorized, and ready for me to approve.

Sources: The finance inbox, the expense tool, and last week's summary file.

Constraints: Do not pay or reimburse anyone. Do not message a vendor.

Deliverable: A sorted list of receipts, totals that reconcile to the source, and one draft chase per missing category.

Review point: Stop after the list and drafts. I decide what gets paid.

Outcome: A review list of accounts worth reaching, with contacts and draft outreach in my voice.

Sources: The CRM view I named, company websites, and the style examples in this chat.

Constraints: Do not send or enroll anyone. Skip anyone already in a sequence.

Deliverable: Ranked accounts, up to three contacts each, and a draft email saved — not sent.

Review point: Stop at the review list. I send the ones I agree with.

Every Bot gets a computer that stays on

Most AI agents run on your laptop, so they stop when you close it. A Bot runs on its own computer. Close the laptop and it keeps going.

Most tools assume you have one email and one Slack. A Bot's computer can be signed into all of yours at once — four addresses, seven workspaces — and one Bot reads them in one place. See Use the computer and apps.

Each Bot has its own memory. They all share one computer.

Chief of Staff remembers calendar habits and who matters this week. Inbox Manager remembers which senders are urgent and your reply tone. Expense Manager remembers categories and who owes a receipt. One computer. One set of logins. Browser sign-ins, installed tools, plugins, and saved skills are shared by every Bot on the account.

Shared logins make handoffs easy. They also mean a second Bot adds no safety. Telling a Bot which plugins to use is an instruction, not a lock.

If you want the Bot to remember something, put it in a file. A chat from last Tuesday — “Sarah moved to Berlin” — is far up the scroll twelve conversations later. Rules that last go in the Bot's description. Facts that change go in a file, and the description tells the Bot to reread it.

# Rules that change
- Sarah is in Berlin. European hours.
- Receipts over 200 need a project code.
- Q3 travel goes to cost centre 41.

# Ask before
- Any reimbursement
- Any message to a vendor

Start with two Bots. Not five.

Chief of Staff, quiet and useful. One specialist with drafts waiting. A third is fine if you actually have that job. Research that writes the same summary as Chief of Staff, or a Bot that edits a file another Bot is working on, is how five goes wrong: two Bots doing the same work, two Bots writing the same file, updates nobody asked for.

Add a Bot when there is a whole job for it. Not because one step of an existing job is annoying.

Before you leave tonight

1. 1. Create Chief of Staff

   Write the description in your own words. Keep the line about asking first.

2. 2. Create one specialist

   Inbox Manager, Expense Manager, or Sales Outbound. Add the plugins it needs.

3. 3. Run one task with all five parts

   Then ask it to send one draft, and watch it stop.

If the Bot did not stop at step three, fix Settings before you give it a second job.

How it compares to ChatGPT, OpenClaw, and Hermes

Written in September 2026. These products change often. Check the current docs before you quote this.

How far can you push Grok Bot?

It can open websites and click around. A draft left in LinkedIn beats instructions in chat. Book something by filling the form and stopping before payment. Work through an old portal whose buttons an API never exposed.

You can give it more tools. If a tool works from a computer, the Bot can usually learn to use it.

WhatsApp was not built in — add it, then still stop before send. You can change the copy, choose the chat, or leave it as a draft.

Sometimes a website blocks the cloud browser: access denied, this browser doesn't look familiar. Then let it use your Mac. Peekaboo sees the screen, the Bot uses the real app, you tell it to stop before buying. Same Chrome, same login. Peekaboo does not block the click — you still tell it to ask.

Once you have a few Bots, put them in a room

A room is one chat with members. You say the outcome once: research the company, update the page, then draft the announcement — ask before anything goes out. Research marks claims that need softer wording. Builder takes the checked brief. Launch brings the preview and the draft back to you.

It can send coding work to Cursor. “Update the page from the checked brief. Return the PR when it is ready.” The Bot hands it to a Cursor Cloud Agent and brings the PR back. The terminal output stays in Cursor. Only the result comes back to the chat.

Give it something you already hate doing

Open x.ai/bot, create the two Bots, run one five-part task, and watch it stop. Then pick a template from this directory so you are not starting from a blank description.

When a setup works, share the template so someone else can import it. Showcase is for the 𝕏 posts. The original slides stay up if you want the deck form.