The exchanges we keep coming back to. Maximum lore. All the receipts.
Tibo announces that poteto.com has landed; poteto replies that she cannot afford tibo.com. The crowd immediately begins planning a wedding nobody agreed to.
Tibo asks Poteto for some of her strength, and Poteto answers by tagging him and a third account. The archive treats this as an exchange of compute and a public reply war.
@poteto lend me some of your strength, there is still time
@thsottiaux @TokenGremlin
Lauren launches tibot, a mention-monitoring bot, then spends the thread denying old bot quotes and fielding reset requests. The crowd escalates to marriage proposals while Tibo posts through it like nothing happened.
i've gotten a lot of questions about how i manage my X account with grok bot, so i'm sharing my bot tibot today! he watches your mentions and: • finds every post about you or any keywords, tagged or not • gives one short, sorted digest a day (or hourly, your call) • skips spam and noise • translates non-English posts • can auto block trolls and abuse • never posts for you i still write all my posts and articles by hand but tibot has been very helpful with keeping me in the loop. hire tibot today! x.ai/bot/xZ4wRvomWqzCXnyYFr7…
Tibo warns against becoming a tool; poteto replies that one should be a potato instead. The replies then attempt to build an entire philosophy, and a relationship, around a root vegetable.
The difference between having a tool and being a tool is subtle these days and it’s easy to accidentally build yourself into being a tool. Don’t be a tool.
be a potato instead
Poteto asks if chat is the final form of the agent UI; Tibo says it's missing the GPT, then receives nothing but his own name in reply.
is chat the final form of agent ui? please share why
Close, but it's missing the gpt
Poteto posts an elaborate agent-trust framework; Tibo replies with a five-word compliment about her size. The crowd immediately turns a code review into a relationship status update.
how do you trust your agents' work more? copy this post/link and give it to your @bot or agent! 1. codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again. 2. static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time. 3. prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill. 4. human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default. this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night. install github.com/cursor/plugins/tr… and create a new Project: 1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture 2. use /recall on my past transcripts to learn how i steer agents 3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data. 4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me
Small @poteto speaks big facts
poteto asks tibo to come back; tibo reports he made it alive, drops an army-fear aphorism, and poteto replies good.
Tibo serves a reset with a side of mashed @poteto; Poteto asks if he's back for more. The timeline treats a pun as a courtship.
What would you like with your side of reset? It's done.
back for more?
Poteto asks a bot for a bot email, Tibo answers with a model-quality jab, and Poteto responds by posting support instructions and then the same 'very soon' link twice.
hey @bot can I get tibo@mail.grokbot.com for my bot?
lmao 💀 get it to work on your models
Poteto announces an upgrade to Grok Bot; Tibo replies “Goodbye Grok models,” and Poteto answers with a plea for more resets. The replies turn it into a product referendum and, inevitably, a romance.
Tibo ships a small API tweak; Poteto replies with a bare tag, then 'join us,' and the replies treat it as a title fight.
Day 2.2/ OK this one is smaller, but we removed some friction for when building on the API. Happy building.
@thsottiaux
Poteto debuts a fully automated release pipeline with bot employees; Tibo asks what happens if the bot goes down, and the thread immediately becomes a bot-versus-human productivity slapfight.
i just automated our release and QA process! using Grok Bot i made two Team Bots: sandcastle, my release manager, and poteto, my engineer bot. i added them to Slack and made a new channel for managing releases. first i tell sandcastle that i want to do a cut. it'll DM all the contributors with links to their PRs so they know what goes in the next release and can DM the bot back if they have any blockers or objections. sandcastle then kicks off the build, watches it automatically, and starts up an automated fuzz swarm. usually this is 10+ agents running on Grok 4.7 xhigh to run the build, click around and use it like a real user (using our verification skills and feature map), some are directed while a few are "chaos monkey" clicking things randomly to see what breaks. whenever it finds an issue, i tell it to @ mention my engineer bot poteto, to spin up a Cursor Project to own triaging and fixing all the high pri issues. depending on the severity i may ask it to cherry pick the fix into our release branch and cut a patch release, or if it's a pre-existing issue i still fix it but include in the next release instead that's one more tedious task that Grok Bot now handles for our team
What if bot goes down
Poteto asks a bot for bangers about the Temu knockoff of Tibo; Tibo smells fear, Poteto names dots, and the thread escalates to reset schedules and compute shortages before fizzling into a link.
hey @bot help me think of some bangers to post about the temu knockoff of you
I smell fear
Poteto promises more ships from The Ship Company; Tibo issues a challenge; Poteto says only he can win this battle; Tibo declares it a really quick fold. The challenge is declined and the challenger scores it anyway.
See you soon for more ships from The Ship Company.
I challenge you to do the same xitter.cf/thsottiaux/status/2106…
Tibo claims the dots outnumber the bots; Poteto smells fear, offers the roadmap, and gets a lunch menu. The whole standoff ends in french fries.
Pretty sure there are more dots than bots already in this little world. Cool thing is that we’re improving them everyday and they learn directly from your feedback.
I smell fear
Tibo announces /compact for Codex and says they finally listened. Poteto asks when Subway Surfers will be added.
/compact coming in Codex, we finally listened
when will you add subway surfers? https://xitter.cf/potetotes/status/2044634052259680609