OC
Joined September 2014
- Tweets7.7K
- Following911
- Followers21K
- Likes19.1K
Pinned Tweet
here's how i shipped 2,500 PRs last month to production
this was originally supposed to be for Cursor Compile in London. i couldn't make it since i was livestreaming for Grok @Bot Galaxy so i'm making it available for free here on X! watch it on 2x speed, i talk slowly
lauren retweeted
I’ve got a problem. I’m addicted to Grok Bot.
I keep finding excuses to make another @grok @bot. Apparently I’ve made 81 bots since August.
So the team gave me 50 codes to give away for a free month of Super ($100 tier).
Haven’t tried it yet? Reply with what you’d build.
I’ll pick 50 of the most interesting ideas. New users only.
ALT Hiten's Grok Bot addiction.
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
grok @bot 0.75.2 is out!
- pages: reports, memos and dashboards your bot builds and keeps up to date
- new cards in every desktop chat
- bots can make videos from a description or an image
and a lot more! read everything in the changelog: x.ai/changelog/bot
ALT Grok Bot 0.75.2: Pages, new chat cards, and video creation
ALT Pages: reports, memos, and dashboards your bot builds
ALT Redesigned cards in every desktop chat
ALT Videos from a description or an image you share
i've been a bit quiet - working on a new companion skill that will help your agents draw these beautiful statecharts/diagrams + check them against the specs you made with /create-formal-verification-skill in pstack!
it now uses Pele from @kepano too which is why they look so good.
will release soon!
there's something really cool about asking your agent to draw a statechart (hypothetical example in this image), then using the /create-formal-verification-skill you made with pstack to find bugs through something like TLA+. you can both understand your code better and how the user flow should work, and fix issues users would otherwise see
lauren retweeted
We gave the whole team a Grok Bot that knows our brand. Now anyone can make a great deck in seconds, and I don't have to worry if someone is using the wrong font.
lauren retweeted
grok bot is by far my most used personal assistant. Apple level product design and seamlessness
i made a grok @bot purely for doing research and making a pdf packet that aligns with the fraud reporting guidelines on america.gov
x.ai/bot/HSx6HHjUF9_F9kL9qA3…
there's something really cool about asking your agent to draw a statechart (hypothetical example in this image), then using the /create-formal-verification-skill you made with pstack to find bugs through something like TLA+. you can both understand your code better and how the user flow should work, and fix issues users would otherwise see
pstack v0.15.27 ships with a new skill /create-formal-verification-skill!
it's still in beta, and similar to /create-verification-skill, this is a meta-skill that creates a new skill and formal verification suite based on the characteristics you want to verify. for example, you may want to model state machines and systems with concurrency using TLA+, or use kani in rust to check for undefined behavior.
if you're new to formal verification, think of it as mathematically proving properties and invariants (something that must always be true) or "laws" of your system. usually, this means modeling your programs in a separate language like with TLA+ and then running the solver on that spec. newer approaches like with kani and @bendlang take a different approach where there is no separate language: you write kani in rust, and bend in bend (it's also a programming language, and the proofs are written as laws and expressed in its type system).
historically formal verification never reached mainstream status because of the difficulty in modeling and writing proofs. it's quite difficult to model your business requirements and keep them in sync! but i expect that we will see more innovation in formal verification in the future as being able to formally verifiy that the code does what you intended gives your agents superpowers in writing correct software.
in the meantime though, i've been experimenting with modeling our code with TLA+ and have already found several bugs with the skill created by /create-formal-verification-skill.
try it out and let me know how it goes!
