I too felt the need for some structure around AI coding, and created a spec-based tool earlier this year: https://www.shipsmooth.net/. I'm happy using it. I think of it as "light-weight" and encouraging iterative development over specs+code. It creates just one spec file and one "tasks" file for each unit of work. Available as a plugin for Claude, Codex etc.

It's still flaky: https://www.isitdownrightnow.com/tornadovps.com.html. They have a blog post regarding the outage (may not load if it's also been affected): https://tornadovps.com/blog/2026/07/distributed-denial-of-se....

As the linked page describes, “Tornado VPS is a focused, old-school VPS provider that has been active since 2005, originally under the Prgmr.com name. They do one thing only – Linux and BSD virtual private servers on Xen – and they clearly target people who already know how to manage a server.”

Their main site (https://tornadovps.com) has been down for hours, and probably all sites hosted on it: https://www.isitdownrightnow.com/tornadovps.com.html

How would this be different from Apple's recently launched "container" utility? https://github.com/apple/container

I feel that flow state[1] is possible as long as you don't feel distracted into doing other things and you're needed to guide the LLM along every few seconds/minutes (someone mentioned a pair-programming type tool in this thread). For me that works if you have a good spec + workflow tool (assuming you're doing interactive coding and not kicking off long running coding jobs). I feel that a good test of a workflow tool is that it should offload all bookkeeping from you, leaving you to just read the generated code and think about design/architecture.

I built one such tool for myself: https://www.shipsmooth.net. You can use it to spec/plan out a piece of work, and then easily keep updating the spec/plan as you churn through its implementation. The tool assumes that you will pretty much end up changing the spec/plan during implementation, based on how it's going. In general, I don't see how it's possible to one-shot high quality code for custom use cases.

[1] Going by the definition of flow state here: https://en.wikipedia.org/wiki/Flow_(psychology): "fully immersed in a feeling of energized focus, full involvement, and enjoyment in the process of the activity. In essence, flow is characterized by the complete absorption in what one does, and a resulting transformation in one's sense of time."

It's possible they are running at a loss at present. But in a recent podcast their founder said he believes inference is profitable, based on their experience serving models: https://newsletter.pragmaticengineer.com/p/opencode (search for "profitable")

It would be interesting to see if LLM's can scan and surface such issues. Might have been probable with parsing tools pre-LLM also? Not sure.

I believe “sessionization” is a common term used for this: https://dev3lop.com/blog/sessionization-in-clickstream-event...

Fairly predictable given the times: a plugin for coding assistants that supports a development workflow that I like :) It's at https://www.shipsmooth.net/.

Perhaps the more interesting bit is that it's in Java (not Typescript or Rust)! Java 25 is pretty neat. Bonus: getting to know how to distribute a self-contained Java program using jlink and the likes: https://docs.oracle.com/en/java/javase/17/docs/specs/man/jli...