
hi
Tibo. Poteto. The crowd. Every public receipt we’ve collected, including the posts between the plot twists.
116 public receipts

hi

i bought a new domain too

💀💀💀 i cant afford tibo.com

@thsottiaux @TokenGremlin

y is he so tired

@4A4133

this is art

the shipping intensifies

wow pstack irl

thanks for the sweet potato

💀

if you click on the All dropdown you can filter out grok bots

this was a poteto original

yes! github.com/react/react/tree/…

love it! thanks for leading the way

yes you can

i stg

cc @johnbai

that was a long time ago!

here's a profile picture you can use for tibot

it can if you give it the X api, but does use api credits

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…

thanks Tibo

@JonasBadalic @bot

let us know how we can make it better!

https://xitter.cf/poteto/status/2115133011352240581?s=20

the Grok Bot team ships quality at an incredible pace! we've invested in making our code friendly for agents, by making the easy thing the right thing. engineers, designers, and PMs all contribute multiple hundreds of PRs a day: fixing bugs, polishing the user experience, and making our apps faster and more reliable. it isn't perfect of course and we do make mistakes, but we aim to learn from each occurrence and improve our workflows so our bots don't make the same mistake twice. i personally think that Grok Bot is the best example today in the industry of where all those tokens are going: quality and velocity, without compromise. something i think people forget in the discussion around token usage is that software development is an iceberg - new features are only a small fraction of the work in maintaining high quality software. and we will keep accelerating and improving!

hire grok bot!

here's one example of expect tests, we used these rigorously for react compiler: github.com/react/react/tree/…

so many gems and great tips in this talk from @yminsky about how to improve your codebase for agents • agents thrive on feedback, and types are one of the best kinds • make illegal states unrepresentable with types, and it enforces global rules across your codebase • property based tests, fuzzing, and even full-system deterministic simulation testing • expect tests: just print stuff out and capture it in the test. makes behavior legible. it's very similar to how compilers have fixture tests, it reduces the review surface area • formal methods used to be very expensive: seL4 is about 8,700 lines of C and took around 25 person-years, with 23 lines of proof for every line of C code, but agents change the roi youtube.com/watch?v=rUYP4C29…