Carlos retweeted
Grok Bot just got Tailscale!
One click, and my Grok Bot can reach the devices on my private network by name. No port forwarding. No exposing anything to the internet. It can reach the machines at home now, and sooner or later, it’ll be able to run most of our digital devices.
Carlos retweeted
Did some reading on formal verification this weekend:
hashcloak.com/blog/tutorial-…
vitalik.eth.limo/general/202…
adam.math.hhu.de/#/g/leanpro…
Absolutely worth reading. Especially vitalik's post if you want spark notes version. FV is hot these days, and it's not just empty hype.
“readability' to agents really means 'verifiability’”
We need to reconsider our priors on code readability.
Humans, compared to agents, are pretty slow at understanding large quantities of text. So in the old days, readability was important so the human could efficiently grok what was going on.
So readability now comes down to:
1. Can a human, if needed, jump in and understand the code
2. Does the code use the same domain language as the human describing the code?
1 helps with observability and the occasional spot checks you need to do on important PR's. 2 helps the agent translate the words you use into code changes.
In other words, readability is now a nicety, not a necessity.
The way agents 'read' code is different - good agents are all about gathering data about how the code works. They'll prod around with it, execute parts of it.
So 'readability' to agents really means 'verifiability'. How easy it is to mess about with that code to see it working.
Let's take this scenario:
- You have a huge module in your codebase that uses all sorts of complex performance tricks
- It has 100% test coverage
A talented human would need an hour or two to get comfortable working in that module.
An agent needs zero time. They verify it with the tests, poke about a bit, and they're good to go.
The takeaways:
- When judging a module (or a codebase), don't think about how easy the code is to read
- Instead, think about how easy it is to verify
- Design your codebase so modules can be tested and verified independently
- Feel free to sacrifice a bit of readability for performance
- Cyclomatic complexity and function size don't matter to agents
251
Carlos retweeted
Subagents are the biggest cause of AI failures
In most harnesses:
1. Main agent writes a summary of what it knows
2. Subagent starts from that summary only, and makes assumptions
3. Subagent works and sends back a new summary of what it did
Same flaw as compaction: all summaries are lossy. This is how your assistant makes emails you never wanted, or purchases what you told it just to get the price of
So I tried something new: checkpoint agents
The initial agent has complete context of what needs to be done. And that input is already cached
Fork the session where it is. Send the fork ahead to do the task and it will do exactly what the main agent would have done; their context is identical
What is even better is when the fork finishes, the cache of the main agent is kept warm by the subagent (they share the same prefix)
I measured it on a 137k-token session with Opus 5.5:
→ Main agent does it on its own: 67 s, $0.38, context +8-17k
→ Checkpoint: 117 s, $0.68, context +2k
→ Classic subagent: 123 s, $0.57, context +4-5k
But here is what I found: avoiding large input is even more important than keeping cache. And most subagent tasks were done better either in series with retrieval, or split up to be parallel over fresh sessions from the start
I do not think there is a place for subagent delegation at all. There should either be a super-agent that orchestrates and does no work, or a long running agent that can retrieve from previous sessions, not a worker that completes tasks partially and delegates the rest to other workers
Don't design harnesses based on our assumptions of human behavior
maybe a hot take but i now consider adversarial reviews mostly a waste of tokens. far better to use those tokens on empirical combined with formal verification. i have updated pstack to use the interrogate skill less, and eventually i think i may remove it altogether
i have found very little value with code review in the abstract, agents tend to just get lost in the nitpicks and yagnis
highly recommended talk - this is the new reality of (AI) coding & engineering. Push to main, no PRs, no human code reviews, irrefutable proofs, orbs... Adapt or die
No pull requests, no code review. We push to main.
Our agents read production logs, watch deploys, grant feature flags, and check their own work end to end.
Here's how we do that:
2
377
@grok @cursor_ai @SpaceXSI Why @bot never replies to my info requests on Grok Bot support tickets? I follow @bot here and have a Grok Bot subs
1
61
Sounds :-) amazing > Frontier AI Audio Music Generation
Repo, paper, demo > github.com/multimodal-art-pr…
1
300
New > AI Scientist v3: An Automated Agentic Scientist research system
The AI Scientist v3 is out: The Agentic Scientist.
GitHub: github.com/SakanaAI/AI-Scien…
Blog: pub.sakana.ai/agentic-scient…
arXiv: arxiv.org/abs/2610.18933
The Agentic Scientist is the 3rd iteration of our automated AI Scientist research system, and the shift this time is from “one agent writes a paper” to “a scaffold of parallel agents orchestrates the full research loop.”
The system now orchestrates a pool of parallel workers that share memory and distilled conclusions. Crucially, it features Evidence Generation: isolated agents automatically run controlled baselines and ablations to prove why an idea actually works.
It works as a co-scientist. We used a development version as a co-scientist to explore biologically plausible learning rules. The agent handled the empirical heavy lifting, proposing mechanisms and running experiments. We stayed in the loop to steer direction, verify results, and moderate claims. That feels like the right division of labor for where the technology actually is.
This resulted in a new biologically plausible learning algorithm, and the resulting paper was accepted at ALIFE 2026 as an oral presentation.
We are also releasing AutoIllustrate. It generates editable draw.io vector figures instead of uneditable, hallucinated raster images. Real scientists need vectors, not pixels. I am an SVG junkie ;)
Incredible work by Robert Lange, Luca Grillotti, Yutaro Yamada, Rujikorn Charakorn, and the team!
340
RSI-Anything: Turns world-model predictions and interaction feedback into recursive self-improvement
Paper: arxiv.org/abs/2610.13912
Repo:: github.com/Gen-Verse/RSI-Any…
Excited to introduce RSI-Anything!
One RSI model that works across coding, GUI, planning, or even Science tasks.
Let's RSI Everything!
📄 Paper: arxiv.org/abs/2610.13912
💻 Code: github.com/Gen-Verse/RSI-Any…
#RSI #WorldModels #RSI #AIAgents #AIforScience #JEPA
Carlos retweeted
I turned @googlegemma EmbeddingGemma 2, an embedding model, into a speech-to-text model, and it turned out to be one of the fastest STT models you can run on device.
On a base M3 MacBook Air it transcribes an hour of audio in about 13 seconds: 288× real time.
The idea came in March with Gemini Embedding 2. It puts text, images, audio and video into one shared space, so a spoken word lands right next to the written word. If that's true, you should be able to read a transcript straight out of the embedding model. I couldnt tried it then, but last week EmbeddingGemma 2 came out as an open model, so I tried it.
Carlos retweeted
You can now train your own Decision model like Jev locally!
We increased Qwen3.5 0.8B’s aggregate accuracy from 20.7% to 74.3% across 3 decision benchmarks - on just 4GB VRAM.
Turn any LLM like Qwen3.8, Gemma 4 into decision models with our open-source Unsloth repo.
We fine-tuned with a Clef head using Unsloth and LoRA (r=64) for one epoch, increasing downstream accuracy from 30–37% to 78%.
GitHub: github.com/unslothai/unsloth
Guide and Notebooks: unsloth.ai/docs/basics/train…
It seems Claude for Startups Program comes with some nasty T&Cs, read the fine print before you sign up.
Replying to @claudeai
The terms for this sucks, and you agree to them by just applying.
- §2.4 Anthropic "may develop similar or competitive technology"
- §2.4 permits reuse, for any purpose, of general ideas, know-how and techniques remembered by personnel looking at your data
- §D.4 prohibits accessing their services to build competing products or services
- §F.1 allows them to retain and perform safety reviews, superseding ZDR (whats the point of ZDR then?)
and it could get worse later!
- §6 permits changes to the addendum at any time without notice or liability
@jason you advising your start ups to apply for this?
[1] anthropic.com/startup-progra…
[2] anthropic.com/legal/startup-…
1
463


























