WeWorkBuddy

Show HN: Pots – Open-source Grok Bot alternative, used by 6 startups for a month

Hi HN, I'm Crokily. Pots is an AI coworker that lives in the chat your team already uses: Slack, Discord, Telegram, or any channel with a Chat SDK adapter. It is MIT-licensed and runs on a machine you give it, with the model you choose. To be honest, the first time I used Grok Bot, its design really impressed me. Unlike OpenClaw before it, it was not just Claude Code connected to a chat app. It truly cared about how it works with people. It felt like a living AI assistant, and working with it wa

Read original source
Source page screenshot: Show HN: Pots – Open-source Grok Bot alternative, used by 6 startups for a month
Source page screenshot · news.ycombinator.com

Source record

Recorded metrics

points · 3 votes
2026-11-11 15:45:06.779Z
cumulative since publication

Research analysis

Project record

Repository: Crokily/pi-durable-bot. Source account: Hi HN, I'm Crokily. Pots is an AI coworker that lives in the chat your team already uses: Slack, Discord, Telegram, or any channel with a Chat SDK adapter. It is MIT-licensed and runs on a machine you give it, with the model you choose. To be honest, the first time I used Grok Bot, its design really impressed me. Unlike OpenClaw before it, it was not just Claude Code connected to a chat app. It truly cared about how it works with people. It felt like a living AI assistant, and working with it wa

Observed adoption & comparisons

Source votes: 3 votes (Nov 11, 2026 UTC; cumulative since publication) Recent records to compare: “Show HN: Lettercamp – open-source static blog framework” (Show HN, Nov 11, 2026); “openai/codex-security” (GitHub Trending, Nov 11, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.

Adoption decision

Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.

Unverified requirements

Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.

Next test

Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.