Also Opus 5 is fine if your codebase is simple.

Their api pricing is absurdly expensive.

I read that and it feels like some theoretical thing versus causing impactful outages for workloads shaped like tailscale’s.

> The bug is a data race with tight timing constraints. It is unlikely to occur in common use.

A large customer did experience this corruption, so it's important for people with tailscale's setup update immediately.

> The developers have never been able to reproduce the bug organically and had to add special testing logic to SQLite that deliberately triggers the circumstances of the the bug in order to verify that the issue has been fixed.

I am not sure why you wouldn't want to use the SOTA models unless speed is a concern. Otherwise you are leaving quality on the table.

The only interesting thing is whether OpenCode is more effective at writing code with it's reduced system prompt.

We achieved significant savings simply by moving everything that varies across individuals out of the system prompt so every session starts from a cache point.

For example you never want your system prompt to start with the time that the session started. Move that to the first user message if needed.

The issue with any AI writing is that it all sounds the same.

Once that stops being true, maybe it will be acceptable. But until then, you are left with repetitive crap. That you must wade through. Not good.

If this succeeds, there is no stopping AI given it will have crossed the rubicon of human bottlenecks.

“Hell no”

> “Umm…”