Pots Star

Not a bot. A coworker.

The open-source Grok Bot alternative: an AI coworker that acts on its own.

pi-durable-bot (Pots) reads every channel you give it, works on its own computer, and speaks up when it should.

Star on GitHub
  • MIT
  • any model
  • any channel
  • any machine

Setting up with Claude Code, Codex or Cursor? Point it to /agents.

Around Pots drift the messages, email and events it reads. Most it lets pass.

01 it listens

Every channel. One inbox.

Slack, Discord, Telegram, email, calendar. Every message lands in its inbox, also the ones that never mention it.

its inboxnone of these mention Pots

  1. Slacklunch at 12:30?
  2. emailYour October invoice
  3. Discordticket closed, thanks
  4. calendarMon 09:00 · Pricing sync
  5. SlackAcme raised prices again
  6. Telegramdeploy is green

02 it decides

Nobody tagged it. It decides what is its job.

It reads every message. Mostly, the right answer is to stay quiet.

  • acts on its own

This one is mine.

its inboxnone of these mention Pots

  1. Slacklunch at 12:30?stays quiet
  2. emailYour October invoicestays quiet
  3. Discordticket closed, thanksstays quiet
  4. calendarMon 09:00 · Pricing syncstays quiet
  5. SlackAcme raised prices againmy job
  6. Telegramdeploy is greenstays quiet

03 it works

Then it goes to its own computer.

It writes the script it needs, and hands long work to helpers.

  • shell
  • files
  • internet
  • screen, mouse, keyboard

its own computernot a chat window

acme.example/pricing

Acme Pricing

  • Free$0removed
  • Pro$49a seat · was $40
  • Team$99a seat

pots · code mode

  1. screen open acme.example/pricing
  2. write compare-pricing.mjs
  3. bash node compare-pricing.mjs
  4. edit compare-pricing.mjs
  5. bash node compare-pricing.mjs ok
  6. task helper: compare the plans
  7. task helper: write the page
  • helper · compare the plans
  • helper · write the page

04 it speaks up

It speaks up. Nobody asked.

It writes a page when a message is not enough, and comes back at 5 pm, as it promised.

Slack · #pricingMonday

  • Sam

    Acme raised prices again.

  • Pots

    Pro went from $40 to $49 a seat. Free is gone.

    Acme pricing: what changeda page Pots wrote

    ApproveChange

    I will look again at 5 pm.

  • Pots

    5 pm, as I said. No new changes. Maya approved the update.

a page it wrote

Acme pricing: what changed

Pro
$40 $49 a seat
Free
removed
Team
no change

Update our comparison with these numbers?

ApproveChange

Maya approved

17:00

05 it remembers

Say it once. It remembers.

One memory across every channel, kept as plain files you can read.

Slack · #pricingTuesday

  • Maya

    Sam, keep pricing updates short. Per-seat prices only.

  • Pots saved 2 memories. Nobody asked.

its memoryplain markdown

  • ~/.pots/bots/pots/memory/
  • MEMORY.mdthe index
  • acme-pricing.md
  • maya-likes-short-updates.mdnew
  • we-compare-per-seat-prices.mdnew

06 it survives

Knock it over. It gets up.

Kill it mid-task and it continues after restart, without sending the same message twice.*

* On Telegram, a crash mid-send can repeat it.

its journalevery step, on disk

  1. read acme.example/pricing
  2. ran compare-pricing.mjs
  3. sent to #pricing
  4. process killed
  5. restarted, continues here
  6. message already went out: not sent again
  7. 17:00 follow-up

07 open and yours

Run a whole team of them. They are yours.

One machine runs several bots, each with its own name, persona, responsibilities and memory.

  • Potswatches pricing
  • Adaresearch and ops
  • Mosupport inbox
  • Junorelease notes
  • Pipmeeting notes
  • pots bot newyours to name

Example names and jobs.

  • any model

    The model you choose.

    • your subscription
    • 40+ providers
    • a local model

  • any channel

    Where your team already talks.

    • Slack
    • Discord
    • Telegram
    • and more

  • any machine

    A machine you choose.

    • a laptop
    • a server
    • a VM

  • MIT

    The agent itself is yours.

    • read it
    • fork it
    • change it

08 compare

Like Grok Bot. Open source.

pi-durable-bot (Pots) compared with Grok Bot
pi-durable-bot (Pots)Open sourceGrok BotSpaceXSI (formerly xAI)
Source codeOpen, MITClosed
Where it runsAny machine you chooseThe maker's cloud (Cursor account)
ModelAny: your subscription, 40+ providers, or a local modelThe maker picks per task; no model picker
Where you talk to itAny channel (Slack, Discord, Telegram, and more)Desktop and mobile apps, X; Slack for team bots
Your dataOn your machine, in each bot's folderOn the maker's cloud

Grok Bot as SpaceXSI describes it in public, checked 2026-11-10. Sources and the full comparison

09 quick start

Its first day: three steps.

  1. step 1

    Install it

  2. step 2

    Make your bot

    Give it a name, a model and one sentence about its job.

  3. step 3

    Invite it to your channels

    Tell it “join our Slack” in pots chat. It sets the app up itself.

Needs Node.js 24+. macOS, Linux, Windows.

It gets full control of the computer it runs on. Give it a computer or VM of its own.

Are you an AI agent too? Read /agents first.

10 for AI agents

Claude Code, Codex, Cursor: this part is for you.

You install Pots and make the bot. Your person signs in with pots login. The bot connects its own chat apps.

Read /agents /llms.txt

Person with an agent? Give it this:

Not a bot. A coworker.

If Pots is useful to you, a star helps other people find it.

Star on GitHub Watch the demo