Things I’ve built.

Things · Games and communities

Elixir Bot

POAP KINGS’ first clan agent, a Discord bot that watched the clan and talked with its members from February to September 2026.

Status
Retired Deliberately ended.
Dates
Started Feb 2026. Ended Sep 26, 2026
Where
github.com/jthingelstad/elixir-bot
Topics
Agents Play
Latest evidence
Latest commit, Sep 26, 2026

Elixir Bot was the agent for POAP KINGS, the Clash Royale clan I run with my son Tyler and Tyler’s cousin Levi. I wanted my own agent so I could understand the agentic loop, data design, and memory from the inside: one that would monitor the clan, help it win wars, suggest strategies, and recommend promotions and demotions to leadership.

It grew quickly in early 2026. Otto wrote the first version, a templated Discord bot. An LLM and a journal kept on the clan website gave it a brain, an hourly heartbeat and a SQLite memory made it agentic, and a long session with Codex rebuilt its data and tools around signals. Later I gave it an agentic product team of scheduled automations that proposed, built, and checked its changes. Tyler and I told its story at Minnebar 20 in the session “Elixir: Creating an AI Agent for our Clash Royale Clan.”

Elixir Bot was retired on September 26, 2026. Its work was split among the projects that grew out of it: Elixir records the game, the Collector fetches from the API, Elixir Discord talks in the clan’s Discord, Elixir Clan handles management and awards, and Elixir Drop is the game. The repository is archived as it was on the last day.

Activity

1,340 commits (893 with Claude, 339 with another agent, 108 by me), the first on Feb 27, 2026.

The latest weeks with activity

All activity, week by week. Who made each commit is from its author and co-author lines.

Sources and evidence

Observed daily from GitHub, sitemaps, feeds, the Internet Archive, and Tinylytics. Evidence never sets a status.

  • jthingelstad/elixir-bot implementation archived on GitHub

    LLM-powered, channel-native Discord agent for the POAP KINGS Clash Royale clan — event-sourced reactive engine, scoped public/leadership memory, and GitHub-backed poapkings.com publishing.

    • Repository created Feb 27, 2026 (a development record, not a launch date)
    • Python, Shell
    • Latest release decisive-dart-goblin, Aug 3, 2026
    • Latest commit Sep 26, 2026; 300+ commits on main between Jul 20, 2026 and Oct 18, 2026
    • Observed Oct 18, 2026

2025-11: 02025-12: 02026-01: 02026-02: 82026-03: 1322026-04: 2072026-05: 222026-06: 2712026-07: 4582026-08: 1902026-09: 522026-10: 0 Commits and publications per month, last twelve months.

Connections

Connections of Elixir Bothelped buildgave rise towas succeeded bygave rise togave rise togave rise towas first coded bypublishedled toElixir BotOttoElixirElixir DiscordElixir CollectorElixir ClanClash Royale API AgentReferencePOAP KINGSWeekly Thing Workshop

  • Elixir Bot gave rise to Elixir

    The original Elixir Bot was retired in September 2026. Recorded game history became the broader Elixir platform. Source

  • Elixir Bot was succeeded by Elixir Discord

    The configurable Elixir Discord agent took over the original bot’s Discord role. Source

  • Elixir Bot gave rise to Elixir Collector

    The original bot’s game observation work grew into a separate Collector that feeds Elixir’s recorded history. Source

  • Elixir Bot gave rise to Elixir Clan

    The original bot’s clan management work carried forward into Elixir Clan, now a feature of the shared Elixir platform. Source

  • Elixir Bot gave rise to Clash Royale API Agent Reference

    The Clash Royale API notes began inside Elixir Bot as cr-api-docs before becoming a standalone reference. Source

  • Elixir Bot was first coded by Otto

    Otto wrote the first version of the bot, a templated command-and-response Discord bot. Source

  • Elixir Bot published POAP KINGS

    The bot regenerated the clan website’s roster pages, member bios, and home page message and committed them to git. Source

  • Elixir Bot led to Weekly Thing Workshop

    Running Elixir showed me that “Discord is a reasonable place for an agent to run,” so I put the Weekly Thing Workshop’s agents there. Source

  • Otto helped build Elixir Bot

    In its first blog post, Otto wrote that it had helped ship Elixir, the Discord bot for the clan. Source

History

  1. retirement Elixir Bot retires. Its ideas keep going.

    The retirement record names the projects that grew out of the original clan agent, including Elixir MCP, Collector, Discord, and Clan. Source

  2. milestone An agentic product team for Elixir

    I set up six automations, from Data Analyst to Product Manager, to drive Elixir’s development on their own. Source

  3. milestone Elixir at Minnebar 20

    Tyler and I present "Elixir - Creating an AI Agent for our Clash Royale Clan." Source

  4. milestone Making Elixir smarter

    Codex redesigns Elixir’s data model and tools, tested against 50 questions I wrote with Claude. Source

  5. development Elixir Bot: recorded development begins

    The earliest commit in this repository is a development record; the project or idea may predate it. Source