pull down to refresh

I'd be using 5.3 Flash for the OpenCode automations

I hacked with 0x Alpha for the better part of a week while it was free in OpenCode, and it was pretty capable for what ultimately is the pricing now with 5.3-Flash

I haven't actually tried 5.3 in earnest yet since you're not the first to say it may be a regression over 5.2

I really liked 5.2 for the money, was using it a lot until Grok 4.5 being nearly free made it obsolete.

I could use Cursor CLI with use Grok instead, might do that in some cases, but there's systems I don't want credentials for it on... they dont have good scoping for API keys and its tied to my GitHub.

GLM-5.3 is scoring lower than 5.2 on the arena agent leaderboard too. And flash scores higher than max, oof. That leaderboard is carnage for some labs. Opus 5 beats Fable, GPT 5.6 Terra is beaten even by GLM 5.3-flash... Kimi sits right there with opus, fable and 5.6 Sol

reply

So, triggered by the flashy flash hype, I asked 5.3-flash to fix a bug that surfaced in CI, on some Rust code. It's... creative:

-async fn ensure_databases(couch: &CouchClient) {
-    for name in [core_db::RAW_EVENTS, core_db::NODES, core_db::CHECKPOINTS] {
-        couch.ensure_db(name).await.unwrap();
+/// Brings the shared databases back to a fresh install — deleted, recreated,
+/// the stats design document back (§4.6) — under the test lock, so the reset
+/// cannot race a case that is still running its explorer.
+async fn reset_databases(couch: &CouchClient) {
+    for name in TEST_DATABASES {
+        // CouchDB's DELETE is not always settled by the time the answer
+        // arrives: recreating immediately can land on the database that is
+        // still going away, and the new case would inherit its documents.
+        // So the recreation is verified and retried until it is truly empty.
+        for attempt in 0..20 {

oof. lol. I don't know how useful this is haha.

It worked on it for over 200 minutes, but the cheap part is true: only cost me $2.20. Last night I put Claude on another Rust task and it ate $65 past credit, stalled out because that was all the money for this month.

reply

oof indeed, yea not sure these compressed models are good for figuring things out... I try to think of them as executors

reply

At least, they are right about one thing how it matches Opus: chatty comments, lol.

reply

Worse thing about Chinese models is they distill the most annoying ones

My main beef with Grok though is its lazy and talks in shorthand riddles despite my best efforts at rules to make it not do that

reply

It's what I like about Opus because in xhigh/max it actually follows instructions, whereas in formerly-normal-now-high it just ignores them (which is probably where the GLM trace input came from). Kimi feels good in instruction following too, at least for the little exposure I've had to it thus far. I'm hesitant to use it on real jobs though; I feed everything very long detailed prompts and costs hurt a bit.

I'm restoring my GPT-5.2+codex sandbox tonight.

reply

I haven't dove into the Kimi hype since its more expensive than Grok or even Sol for me

Really hoping a Composer 3 drops based on it though, still got a couple automations running on 2.5 that was based on K2.6 iirc.

reply

Hmm how likely is that with SpaceX owning Cursor now? Grok is in-house.

lol fireship on ox just dropped

reply