The domain-name arms race
Tibo launches poteto.com. Poteto says tibo.com is out of budget.
Great minds. Petty replies.
Every roast. Every reset. Every receipt.


Tibo launches poteto.com. Poteto says tibo.com is out of budget.
Tibo (@thsottiaux) publicly asks Lauren (@poteto) to “lend me some of your strength, there is still time” (main post). Poteto replies by tagging Tibo and @TokenGremlin (main post). Community reactions range from playful power-handover and “Tibo eating poteto” jokes to a mock rom-com question about running off to start a lab together. No private motives, metrics, or outcomes are established.
Poteto introduces tibot, an X-monitoring bot, and follows up with a profile picture.

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…
Poteto publicly thanks Tibo, and the internet does its usual thing: a little light teasing and a lot of potato energy.

thanks Tibo
The main post is poteto tagging @alexandr_wang and @thsottiaux — a bare mention with no further text. Tibo's nearby posts (reset, midnight PST, 'Not a real improvement, put the reset in the bag') are supplied as inference candidates, not as confirmed replies to the tag, so this recap treats them as a loose thematic cluster rather than a proven thread.

@alexandr_wang @thsottiaux
Tibo (@thsottiaux) posted a three-step joke: quit posting butts, buy containers, celebrate your 12 users. Poteto (@poteto) replied tagging Tibo and @alexandr_wang, keeping the exchange going without adding new claims. The recap should stick to the quoted lines and avoid inventing a winner or private context.
Tibo (@thsottiaux) posts a caution against accidentally becoming a 'tool' rather than merely using one. Poteto (@poteto) replies with the concise counter-slogan 'be a potato instead.' The exchange is a one-line deadpan pivot from a serious-sounding warning to a vegetable, and community replies lean into the potato bit and note the two accounts appearing together.
A new public exchange between Tibo and Poteto. Follow the original posts below.

the grok bot team is shipping at a incredible pace! please keep sending us your feedback and bug reports, we will continue working hard on improving and polishing grok bot so it's the best assistant and employee you can hire
A new public exchange between Tibo and Poteto. Follow the original posts below.
Poteto asks whether chat is the final form of agent UI. Tibo spots a missing suffix.
Poteto shares advice on trusting agent work. Tibo says she is speaking facts.

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 https://github.com/cursor/plugins/tree/main/pstack 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 return. Tibo reports survival. The army gets a mention too.
A new public exchange between Tibo and Poteto. Follow the original posts below.

@bobjones @bestTomever @tibo @thsottiaux
Tibo serves a reset with a side of mashed Poteto. Poteto asks if he is back for more.
Tibo calls time on the exchange and wishes the b/dots well. Poteto replies “gg.”
A new public exchange between Tibo and Poteto. Follow the original posts below.

@RealFlyingHigh @thsottiaux
Poteto asks for a bot address bearing Tibo’s name. Tibo has model-related feedback.
A Grok Bot upgrade prompts a model jab from Tibo and a reset reply from Poteto.
A new public exchange between Tibo and Poteto. Follow the original posts below.

@poteto mind looking into this one? Could use some PRs
Tibo diagnoses the compute. Poteto offers a familiar nudge.
Tibo ships an API improvement. Poteto extends a two-word invitation.
Automation, uptime, nothingburgers and a Hello World tutorial all end up in one thread.

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
A new public exchange between Tibo and Poteto. Follow the original posts below.
Poteto announces bedtime and temporarily clears the runway for Tibo.

alright @thsottiaux im going to bed you can post without fear now
A new public exchange between Tibo and Poteto. Follow the original posts below.

@thsottiaux
Tibo announces an Auto-review update. Poteto requests the usual order.

Day 2.1/ We have made Auto-review free for all users signed in through a ChatGPT account. You can enable it in settings > permissions > auto-review. Auto-review improves upon the default sandbox setting that requires you to approve everything, which is prone to decision fatigue unless you spend a lot of time configuring specific rules. It allows you to run long tasks while having a second agent review all actions taken by the primary agent. Its only goal is to prevent high-risk actions from being taken and to protect against unwanted actions that are not aligned with the original user intent. This Auto-review feature is now free and does not draw usage from your plan.

just put the reset in the bag bro
Tibo calls upon Poteto. Poteto materializes with a one-word reply.
A “Temu knockoff” prompt kicks off another round of dots-versus-bots sparring.
Poteto promises more ships. Tibo issues a challenge. Poteto says only one of them can win.
Tibo counts dots. Poteto smells fear. Somehow, lunch becomes a counterattack.
A Codex feature announcement meets a very different feature request.
You’re all caught up.
The lore is a renewable resource.