Config Bots

You have seen one of these. Now have one.

Everyone has watched a clip of an AI clearing somebody's inbox or answering their website at 3am, and then found out it takes a weekend and a developer. This is that, set up in an afternoon, by you.

  • The one that reads your email and writes the boring replies
  • The chat box on a website that actually knows the answer
  • The thing that watches a page and tells you when it changes
  • The one that writes the report nobody wants to write
your-first-bot Ready
  1. 7:00 AM Scheduled run fired. Every weekday, before you are up.
  2. 7:00 AM Read what came in overnight.⚑ email 47 unread, 12 of them worth your time.
  3. 7:01 AM Sorted it. 9 it can answer, 3 that need you, 35 that need nobody.
  4. 7:02 AM Wrote the nine easy replies.⚑ email In your words — it has read a year of them.
  5. 7:02 AM Stopped. Nothing sends without you. Approve from your phone, or edit first.
What you wake up to

9 replies drafted · 3 flagged · 35 archived

Waiting in your inbox and on Telegram.

Where it lives

It goes where you already are. You don't go anywhere new.

A bot nobody opens is a bot nobody uses. So it turns up in the app you already have open — and on your own site, where your customers already are.

Telegram Slack Discord iMessage Email Your website Your own app A mini app

A chat box for your site

Paste one line into your page and your bot is answering visitors, from your own policies, in your own tone. No plugin, no developer.

A web address of your own

The same bot behind a URL only you control, so whatever you built can just call it. Your token, your rate limit, your rules.

Small apps it builds itself

Ask for an intake form, a status board or a dashboard and it ships one — 9 ready-made to start from.

What you hand it

It gets what you give it. Nothing else, and nothing quietly.

14 things you can hand over, one at a time. “Read my email” and “run things on a computer” are separate decisions, not one blanket yes — and anything that leaves the building waits for you first.

  • file system Keep its own files, notes and memory
  • shell Run commands on a sandboxed machine of its own
  • web browse Read pages, call APIs and drive a browser
  • email Read your mail and draft replies to it
  • messaging Message you on Telegram, Slack, Discord or iMessage
  • web scrape Pull the useful parts out of a page it read
  • code execution Run code on its own machine, not yours
  • project management Schedule and manage its own work
  • web hosting Put something live on the internet
  • orchestration Hand work to other bots, and open coding sessions
  • miniapps Build small forms, pages and dashboards
  • vault Use a login you connected on purpose
  • mcp Connect to the other tools you already use
  • voice Send and listen to voice notes
Playbooks

You don't start from a blank box. 23 jobs, already written down.

A playbook is the actual steps for one job you keep having to do. Add one and your bot knows that job. Change a step and the change stays with your bot, not with everybody else's copy.

Morning brief Inbox triage Support triage Daily standup Meeting prep Research digest News digest Price watch Weekly review Content pipeline Client follow-up Expense log Bug to code session Document drafting 9 more …or write your own

It remembers

What you told it in March is still true in June. You correct it once.

It watches the clock

Work starts without you opening anything. Every weekday, or when something changes.

It can use 45 skills

Switch one on and it gets better at that job. Every one is plain text you can read.

It asks

Nothing is sent, posted or bought in your name until you have said yes.

Get started

Pick a job you hate. Hand it over.

Start with one — the inbox, the report, the thing you keep meaning to check. 3 free days and credits to spend, so you can watch it work before you pay anyone.