Julio retweeted
Effect v4 is here.
One ecosystem. Zero dependencies.
The next chapter of Effect and the foundation for building reliable software and AI agents in TypeScript.
Julio retweeted
I only have one thing to say to the AI Doomers:
Pace deez open weights
Introducing Bolt Forge. Free until Oct 14th:
- Up to 50x more usage
- The new frontier: GLM, DeepSeek, Kimi
- Zero usage charges
Live now in your model picker on bolt.new
And one more thing... 👇
Julio retweeted
50x more usage with no usage charges. That math only works on open models.
Bolt Forge runs on DigitalOcean Serverless Inference, with GLM 5.3, Kimi K3, and DeepSeek V4 Pro in the picker.
Congrats @boltdotnew. 🎉
Julio retweeted
A truly standout website costs tens of thousands of dollars in design.
So we did it for you, with a handful of the world's best designers and agencies. For free.
Introducing the Bolt Template Marketplace: real, full stack apps you can open in Bolt and make yours 🧵
Introducing: Bolt Templates
Julio retweeted
There's a whole new way to use skills in Bolt.
Every skill your teammates build is now yours too. And they stack: one prompt triggers all of them, automatically.
Here's how it works 🧵
Julio retweeted
Today we're open sourcing Bolt Slides.
Now any agent (Claude Code, Codex, Bolt) can make slides you couldn't even imagine before.
What does that mean? Take a look 👇
Julio retweeted
Internal tools are the most underrated use case for AI building.
Everyone's showing you consumer apps and landing pages. Meanwhile the operators are quietly building the software that actually runs their companies.
11 internal tools real people are building right now that they could never have built themselves 12 months ago:
1. The CRM that fits the actual sales process. Not Salesforce bent into shape. The founder who lived in a colour-coded spreadsheet builds a pipeline with the exact five stages their deals really move through. The person who closes the deals designs the tool.
2. The inventory dashboard for the warehouse. Ops lead describes how stock actually flows, gets a live view of what's low and what's stuck, instead of a monthly stocktake nobody trusts.
3. The expense approval tool finance always wanted. Submit, route, approve, log. The workflow finance has run manually for years, finally automated by the finance team itself, not a six-month IT ticket.
4. The onboarding portal HR builds in an afternoon. New hire forms, leave requests, the document checklist. The person who runs onboarding builds the thing that runs onboarding.
5. The ops KPI dashboard that pulls the numbers nobody had time to pull. Daily metrics in one place, updating live, instead of someone rebuilding the same deck every Monday morning.
6. The support triage board for the team drowning in tickets. Incoming requests sorted, assigned, tracked. Built by the customer success lead who actually feels the queue.
7. The project board shaped like how the team really works. Not a generic Kanban template. Columns that match this team's actual handoffs.
8. The spreadsheet that finally became an app. The shared file with twelve tabs and three broken formulas turns into a live tool the whole team reads off. Everyone's secret first project.
9. The budget tracker for department managers. See the spend, approve the spend, no more emailing the finance team to ask where things stand.
10. The recruiting board for the hiring push. Candidates, stages, notes, all in one place, built by the person actually doing the hiring.
11. The field-capture form feeding a central dashboard. Team in the field logs data on their phone, it lands in one operations view back at HQ. Built by the ops person who knew exactly what was missing.
These aren't hypotheticals. They're patterns that show up over and over in @boltdotnew.
Notice what these have in common. None of them are flashy. None will trend. Every one of them is software somebody needs to work on Monday.
Software was never limited by who understood the problem. It was limited by who could build it, separated by a backlog and a two-quarter wait, or a new SaaS tool to add to the list.
That gap just closed. The operators (marketing, ops, PMs) who live inside a workflow can finally build the workflow themselves.
The person who understands the problem can now build the solution.
Julio retweeted
I HOPE OPENAI CLONES BOLT.NEW
I HOPE SUNDAR SHUTS OFF THEIR PUBLIC API
I HOPE DARIO ONLY GIVES MYTHOS TO OUR COMPETITORS
WHEN THE ENDING IS KNOWN AND THE DISTANCE IS UNKNOWN, THAT'S WHEN YOU KNOW WHO YOU REALLY ARE. STAY HARD
Julio retweeted
Bolt is now SOC 2 Type II compliant.
This is the foundation that lets people build on Bolt with confidence.
Thank you to everyone who helped us get here.
Julio retweeted
Today we’re thrilled to announce our strategic partnership with @Microsoft.
For enterprise organizations that run on Microsoft this is a game changer.
Getting access to new AI tools in an enterprise is hard.
Today we partnered with @Microsoft to make it easy.
For Microsoft customers, Bolt is:
• Procurement-ready: buy through your existing Azure agreement
• Where you work: build apps from a Teams conversation in minutes
• Extensible: deploy to your own Azure infrastructure
Everyone builds. Engineering ships.
bolt.new/blog/news-press-rel…
Julio retweeted
The trifecta of collaboration launches is complete 💪🏻
This is a MASSIVE upgrade, especially for teams. If you haven't tried @boltdotnew recently, now is the time
Here's what just dropped 🧵
Julio retweeted
Opus 4.7 is live in bolt.
The best app builder needs the best model underneath it. 4.7 is that model - highest score we've ever clocked on long, complex builds.
Go ship something.
Julio retweeted
You've probably seen all the incredible Pretext.js examples by now...
But here's a tutorial showing EXACTLY how to implement it in your @boltdotnew project, wrapping text around a 3D model of a Porsche using @threejs
TYSM @_chenglou for open sourcing 🙏
& @solarise_webdev, @birdabo, @kho, @VladArtym & @mhauken for the inspo!
p.s. edited with @TellaHQ... this tool is incredible
Julio retweeted
The Vibe Jam is back and @boltdotnew is co-sponsoring this year with @cursor_ai. $35K in prizes, one month to build a browser game with 90%+ AI-generated code.
Last year was wild, this year is going to be on another level. Go build something. Link to enter in @levelsio's thread.
Julio retweeted
Today we're releasing Design System Agents.
Upload your design system, and Bolt gives you an agent that builds with your real components.
It lets your whole team build prototypes using your real production UI, so what you design in Bolt is much closer to what engineering will actually ship.
Julio retweeted
Every AI coding tool has the same problem: the output looks like it was built by someone who's never seen your product.
Bolt's bet here is that design systems are the missing constraint. Feed the agent your components, your tokens, your code standards, and the prototype stops looking like a generic template with a gradient.
The "AI slop" framing in that video is the tell. They know the criticism. Every PM who's demoed a Bolt prototype to engineering has gotten the same response: "cool, now we rebuild it from scratch." The design system agent is supposed to kill that rebuild step.
The question is whether it actually works at the component level. Design systems in practice are messy. Half the tokens are outdated. The Figma file disagrees with the codebase. The npm package hasn't been updated in six months. If the agent inherits those inconsistencies, you get on-brand slop instead of generic slop.
But if it does work, the lock-in is obvious. Once your design system lives inside Bolt as an executable agent, switching costs go vertical. Every prototype your team builds reinforces the system. Every new hire onboards through it. The design system stops being a reference doc nobody reads and becomes the literal engine that produces your UI.
That's the real product. The prototyping tool is the packaging.

























