DebugAI retweeted
Every dev has a number they've never seen...
I'm building something at @debugai_x that shows you yours. No one's done this in dev space yet; devs are gonna love it...
comment your guess or RT n I'll count you in for early access.
He ( Mohi ) loves these types of mathematical equations to figures animations. Great work, Yeah this weekend would be really worth. Stay tuned.
Replying to @built4us @debugai_x
For the ones who'd rather decode them: the same three as equations. Every line in this video is drawn by the equation printed under its figure. Follow @debugai_x for the reveal this weekend.
6 · 48 · 16
Count them in the figures. The first one is out this weekend.
Replying to @built4us @debugai_x
For the ones who'd rather decode them: the same three as equations. Every line in this video is drawn by the equation printed under its figure. Follow @debugai_x for the reveal this weekend.
DebugAI 2.12 is out.
From 2.10 to 2.11, "Index Entire Workspace" indexed zero files, so answers only knew the files you'd happened to open. That's fixed, and a debug now sends less from your machine.
Update, then run Index Entire Workspace once.
What a debug stops sending in 2.12:
- your git diff, branch name and changed file paths. Our API never read any of it.
- code from a focused .env, key or credential file. The error still goes, and the status bar says what was held back.
The engine moved to Claude Haiku 5.5 on 10 Oct. We ran it on 12 real bugs from our own history before switching. The numbers are in the post, including one fix it now gets wrong.
Agents: npx -y @debugai/mcp setup
debugai.io/blog/debugai-2-12
DebugAI has its own account now. Releases, fixes and the occasional embarrassing bug, starting with this one.
2.12 lands today at 8:30 am PT.




