Tired of burning tokens every time you rerun the same AI workflow? Now you can turn your best prompts into permanent local desktop apps for free for a whole month!
Get FREE Lite membership for 1 month + 10,000 points, no strings attached.
install KroWork to your desktop and enter the code FDIEHBTI to become a Beta user right now!
https://t.co/Fx97G7QlRa
@AndrewCurran_ GPT-5.6 is already on track to become another Fable 5
its exactly why keeping your data and workflows local matters, when everything lives in the cloud, you’re always one order away from getting blocked
GPT-5.6 just gonna become another fable 5
here we go again, same story, just one month later...
the importance of keeping our data and workflow locally is to avoid things like this
🚨 BREAKING: U.S. government will decide who gets access to GPT-5.6
OpenAI will release GPT-5.6 only in a limited preview to a small group of partners.
Sam Altman told staff the government would be "approving access customer by customer."
Commerce Sec Lutnick personally called Altman warning: don't launch without approvals from other agencies.
A de facto licensing regime.
ITS HAPPENING
here we launch again, after a whole month
check out our latest features as well as our viral new staff-pick Kro App
Cup Odds⚽️: Your best FIFA World Cup Prediction buddy
Persona Distiller👩🔬: You guys already know what this one means😏
and a little gift for early stage users, all in the threads👇
Create your first AI-native App with natural language
meet KroWork 0.9.X
one month, with 5 new versions shipped, here is what’s new:
1. Intelligent Apps: software with built-in AI
2. Share the app you build with One-Click
3. Multimodal capability & latest models support
Your best AI workflows should become real desktop apps, with NO tokens burnt on reruns
Some real cases below to show you how it works:
@milesdeutscher If open-weight models can reliably win in coding, agents, and long-horizon tasks, the pressure moves from model access to product integration, evals, and distribution
@BullTheoryio The next SaaS interface is probably not another dashboard, but an agent embedded where work already happens. The hard part is trust, permissions, and evals — not the chat UI.
this shows the bigger loop pretty well: use KroWork Browseruse to automatically gather context, let AI reason over it, then package the whole thing as a Kro App
Check below a demo video of how we could export/import Kro App and how we pull off a FIFA Odds Software by using BrowserUse and build-in AI function to make the prediction ⚽️
@teortaxesTex Switched coding from 5.5 to Fable for speed. Quality negligible difference for 95% tasks, but 2s vs 6s = stay in flow. Throughput > peak intelligence for iterative work.
@kyliebytes Real adoption signal: non-technical users noticing quality without knowing which model. Best products feel good at every tier, not just top.
What we learned after trying this for two weeks: total token spend dropped 40% while output quality went up.
The thinking model burns fewer tokens because it only handles the hard parts. The execution model burns more tokens but they're cheap ones.
Match the model to the task. It's that simple.
We've been doing this wrong for months.
One model. Every task. Thinking, planning, coding, reviewing, debugging. All of it thrown at the same context window.
Turns out splitting the work between two models produces better results at lower cost. And someone just showed receipts.
The pattern extends beyond coding:
Research: use a deep-thinking model for synthesis, a fast model for data retrieval.
Writing: use a creative model for drafts, a precise model for editing.
Analysis: use a reasoning model for insights, a coding model for the pandas scripts.
Every workflow has a "thinking" phase and a "doing" phase. They're best served by different models.