iiinova — where your digital self keeps evolving

Quint @quint-lang.org · 17/09/2026

Don't you love when you're randomly listening to a podcast while working, and you hear yourself mentioned? Great conversation with Tessl on the @ainativedev.io podcast about their dark factory. Quint got a shoutout for helping provide effective guardrails along the way.

110

Quint @quint-lang.org · 14/09/2026

The beta's still open if you want in: bit.ly/4wr3FK9

000

Quint @quint-lang.org · 14/09/2026

The early reviews are in, and we're grateful. Thank you to everyone testing Quint Studio and telling us what you think. And these are only the public notes. The private feedback has been just as generous 💜

111

Quint @quint-lang.org · 09/09/2026

Quint Studio gives it to you straight.

140

Quint @quint-lang.org · 08/09/2026

Say hello to Quint Studio! Software is full of decisions about how things should work: what happens first, what gets retried, who can do what, and what should never happen.

140

Quint @quint-lang.org · 07/09/2026

Agents like to flood. We like to grow.

111

Quint @quint-lang.org · 03/09/2026

Remember when programming was fun?

151

Quint @quint-lang.org · 01/09/2026

AI changed where the knowledge about your software lives. You might be reviewing code you didn't write and leaning on tests you didn't create.

130

Quint @quint-lang.org · 31/08/2026

AI can generate the code and the tests. The pain now lies on knowing which software behaviors those tests actually protect.

110

Quint @quint-lang.org · 20/08/2026

A special thank you to @mizchi.bsky.social and the wider Japanese community. We are grateful for the attention and excited to see what you all build next.

110

Quint @quint-lang.org · 20/08/2026

The Quint community has been busy this summer, from bug hunts in production systems to freshly verified consensus protocols. A few highlights we loved seeing:

131

Quint @quint-lang.org · 30/07/2026

Join the growing group of Quint users on Telegram, we'd love to have you. bit.ly/3TkzaHp

010

Quint @quint-lang.org · 30/07/2026

We're also building Quint Studio. The decision layer between generated code and production. Join the waitlist to be the first to know. bit.ly/4wr3FK9

110

Quint @quint-lang.org · 30/07/2026

If you'd rather start with AI assistance, Quint now ships as agent skills that work with any coding agent, not just Claude Code. gh skill install quint-co/quint --all --pin main Or through the plugin marketplace. /plugin marketplace add quint-co/quint /plugin install quint@quint"

110

Quint @quint-lang.org · 30/07/2026

When you're ready to go deeper, we have a set of lessons that will walk you through the language step by step. From Hello World, to full protocol anatomy. bit.ly/44XzNt0

110

Quint @quint-lang.org · 30/07/2026

We have a great five-minute guide to get started. You'll be able to install Quint, write your first spec, find a violation, and fix it. bit.ly/3S04n29

110

Quint @quint-lang.org · 30/07/2026

Curious about Quint but not sure where to start? This thread covers the open source tooling, and a quick word on what's next 🧵

141

Quint @quint-lang.org · 28/07/2026

When Charles Hoskinson and his 🐙 call Lean + Quint + Rust "the stack of stacks of stacks," we'll take it. Nothing makes us happier than seeing Quint pushed in ambitious new directions.

142

Quint @quint-lang.org · 17/07/2026

If AI writes the code, what's left for engineers? @bugarela.com's answer on the @infoq.com podcast: the work that always required the most thought. Defining correct behavior, reasoning about every ordering of events, catching the edge cases. AI won't take the fun part away.

131

Quint @quint-lang.org · 07/07/2026

Three fixes. Three violations. One that held. Quint tested every variant exhaustively across all 6-step interleavings. Not sampled, proven. That's the difference between "this probably works" and "this cannot fail."

120

Quint @quint-lang.org · 03/07/2026

"Who knows what's right and wrong is the person building the application. There's so much judgment involved in that." @bugarela.com on what AI still can't decide for you, from her chat on the DevNTell podcast.

121

Quint @quint-lang.org · 02/07/2026

Big update to our LLM support. Quint now has easy-to-install agent skills with our main techniques for writing specs and modeling systems. If you've been meaning to write your first formal specification, today's a good day to start.

251

Quint @quint-lang.org · 29/06/2026

New post on what that means for engineering organizations and why we're building Quint: bit.ly/3RcE3kV

141

Quint @quint-lang.org · 26/06/2026

Great Article by Adam Chlipala on Why Software Requirements Get Easier in an AI Economy. Formal verification is only helpful if you know what to verify. The spec you check needs to match your intents about what is possible and what shouldn't happen.

111

Quint @quint-lang.org · 24/06/2026

The Balancer V2 exploit looked like a simple rounding bug. It wasn't. 🧵

110

Quint @quint-lang.org · 19/06/2026

GitHub Linguist shipped with native Quint support! If your Quint repo has a # mode Bluespec annotation, you can remove it. .qnt files now get proper syntax highlighting and language detection. Our Bluespec era is over. 👋

041

Quint @quint-lang.org · 03/06/2026

Josef Widder is giving a tutorial at FORTE next week on formal methods for distributed protocols with Quint.

130

Quint @quint-lang.org · 02/06/2026

This matters more now because AI is pushing all the thinking up front. Specs are suddenly central. A new wave of tools is calling "writing Markdown for an LLM" spec-driven development. But specs are much more useful when they are precise and executable.

120

Quint @quint-lang.org · 02/06/2026

Even with Quint, the harder question stayed: how do you know your spec is actually done? Three techniques to build that confidence: → Model failures, test past your tolerance → Write witnesses for the rarest scenarios → Capture concurrency bugs as reproducible traces

120

Quint @quint-lang.org · 02/06/2026

We wrote TLA+ specs at Informal Systems for years, but the syntax kept most engineers out. Quint was built to fix that with familiar syntax, type checking, and a simulator for fast feedback cycles. Default mode is simulation, not exhaustive model checking.

120

Quint @quint-lang.org · 02/06/2026

"There is no magical checkmark for software correctness." At Bug Bash 2026, @bugarela made the case for chasing confidence instead, and showed why the AI era raises the stakes. Here's a breakdown 🧵

151

Quint @quint-lang.org · 28/05/2026

Quint just got merged into GitHub Linguist. Starting with the next release, GitHub detects Quint as a language: syntax highlighting on .qnt files and Quint in the language stats bar. One requirement to qualify: hundreds of repos outside the maintaining org. We're in!

081

Quint @quint-lang.org · 26/05/2026

New Quint emote just dropped 👀

051

Quint @quint-lang.org · 14/05/2026

Thanks for building and sharing!

010

Quint @quint-lang.org · 14/05/2026

Lucas Marques built quint-connect for Elixir: run Quint specs as model-based tests on real code, turning state-space exploration into ExUnit assertions. Now published on Hex. bit.ly/3PD0RcQ

130

Quint @quint-lang.org · 14/05/2026

Binil Thomas specced Warmly's session lifecycle in Quint. The model checker found three production bugs that code review and unit tests would have missed. "There's a class of bug review can't see." bit.ly/4u91sSp

120

Quint @quint-lang.org · 14/05/2026

phiat built Quint Crawl, a full turn-based RPG where every game rule is formally specified in Quint and tested via MBT against an Odin implementation. bit.ly/4d7EsgO

120

Quint @quint-lang.org · 14/05/2026

@zicklag.dev is speccing the Roomy arbiter, a distributed group membership service for ATProto. Quint gave him insight and understanding, also helping him find async states he didn't know he had. bit.ly/4dp8pIc

140

Quint @quint-lang.org · 14/05/2026

Four more things the Quint community built and shared. A production session lifecycle, a distributed app spec, formally verified RPG, and Quint Connect for Elixir.

171

Quint @quint-lang.org · 07/05/2026

We worked with Category Labs and Monad on an independent review of MonadBFT, running the Quint simulator for days across two variants of the spec.

150

Quint @quint-lang.org · 06/05/2026

Three ways to drive testing from a Quint spec, depending on how much control your runtime gives you: → Model-Based Testing: replay traces from the model → Hybrid: model proposes the next action based on results from runtime → Trace Validation: capture from production, check it against the model

150

Quint @quint-lang.org · 28/04/2026

New podcast with @bugarela.com on @ColorsofWeb3pod talking spec-driven development and how we benefit from precision and executability of specs, especially in the AI era. Why specs can't just be English and markdown↓

152

Quint @quint-lang.org · 27/04/2026

Quint Studio will be your command center for system behavior. From your first idea all the way to production. Intent, code, tests, runtime monitoring. All connected.

110

Quint @quint-lang.org · 27/04/2026

The Quint team is locked in on building Quint Studio. Here's a bit more about what we're working on and how you can get involved.

161

Quint @quint-lang.org · 24/04/2026

The Quint team is at Bug Bash by @AntithesisHQ this week. @bugarela took the stage to make the case for "Behaviours as the backbone of software correctness."

030

Quint @quint-lang.org · 22/04/2026

What will Quint find in yours? bit.ly/3QCTQc5

020