The last GA (non-preview) release of an LLM from Google was gemini-2.5 in June 2025. 9 months ago.
Since then we've seen Claude 4.5/4.6 and GPT 5/5.1/5.2/5.3/5.4.
Why isn't Google releasing any more models in GA?
coding agents won't kill open source
which is faster?
1. fully research, spec, plan, generate, and verify your own bespoke standards-compliant http stack and web application framework in Rust
2. use axum
repeat for json, sql, s3, kafka, OS, containers, k8s, etc
I prefer "verification" over "backpressure" for coding agents
backpressure implies resistance. but we want faster loops, not slower
verification provides signal back to the generate step. fewer, faster iterations to convergence
a single IMPLEMENTATION_PLAN .md grows unbounded and wastes context, or requires constant lossy maintenance
instead, decompose tasks within specs so agents can explore via progressive disclosure
and track status via emojis:
๐ฒ Not started
๐ In progress
โ Complete
@headinthebox while you are still experimenting with a loop I extended mine to a spiral and added rotation in a second orthogonal plane to form a clifford torus. my claude Code now optimizes skills across the multiverse.
OG surely has better magic spells than me
but I've made it pretty far reading posts, watching videos, putting in reps, incrementing weight, burning tokens
the techniques are effective on 5-10yr old brownfield enterprise Scala services. but always hungry to learn more!
as soon as i post it
corps will rebundle it and sell it
whereโs the upside for us et al topics
heck i even had a frontier lab in my DMs
after posting the above tweet
i was seriously considering moving to SF
to join them but they said no
but now they are in my DMs asking for the solve lol ๐
I assumed Claude Code put the skill content in a tool result, but it's actually in a synthetic user message sent after a tool call.
Using @LangChain LangSmith's Claude Code hook you can see the tool call & user message.
I'm curious why the user message? Drives the model forward more effectively than a tool result?
You can see that CC called the Skill tool with argument "skill: write-dope-haiku" and the result is only "Launching skill: write-dope-haiku".
The following user message (which I didn't send) contains:
Base directory for this skill: /path/to/skill
<contents of SKILL .md file>
I really like the progressive disclosure structure of Loom's specs https://t.co/wSR5xGWdnQ
Seems like a good idea for plans/tasks too. Single IMPLEMENTATION_PLAN .md gets too big.
key component of GH's Ralph: self-updating status checklist
plan .md contains:
# Status
- [x] Phase 1
- [ ] Phase 2
- [ ] Phase 3
prompt .md contains:
study @ plan .md complete the next task only then update the status checklist
cat prompt .md | claude