1/ Introducing the Cua Spaces SDK.
Every big lab now ships a bot with its own computer: Grok Bot, Muse, dots. None let you bring your own. With Cua Spaces, now you can.
Put Claude Code, Codex or any agent on compute you choose, and run jobs across all your computers at once.
David Montgomery retweeted
We'll be spending a lot more time trying to understand the outputs of language models. A few thoughts, tips & tricks:
Writing. Something I've had success with: Ask your LLM to explain something in ASD-STE100, it's a controlled language specification originally developed for aerospace maintenance documentation. LLMs well-versed in this language and it comes with heavy constraints on clean writing style that I often find a lot more readable. Sometimes I've tried to soften it a bit e.g. ask for "80% of the way to ASD-STE100" because the spec is quite stringent. But even better:
Diagrams / images. Instead of writing, ask your LLM to create a diagram. These can be a lot easier to process, parse, and understand. But even better:
Web pages. Ask for output "in HTML" to get a beautiful, interactive webpage. LLMs are getting really good at frontend and can create beautiful experiences, animations, etc. But even better:
Explainer videos. The output format I am most bullish on is fully custom / bespoke explainer videos generated on any arbitrary topic. Experiment with things like "Create a 3b1b style video explainer on X. Use my ElevenLabs API key for audio narration". (you'd need an API key for the latter or you can ask your LLM to find you decent free alternatives that use your local compute). This is actually starting to work!
In summary:
- As LLMs get better, they will do more and more of the legwork autonomously, and a lot more of our work will rise up the abstractions into oversight and understanding.
- Luckily, LLMs can help here too because as intelligence and code are increasingly abundant, you can ask for large, custom, discardable software artifacts (e.g. web apps, video explainers) that would have never made sense to create before. Push the boundaries here and you'll be surprised.
David Montgomery retweeted
we tend to keep a very low profile at @ssi
however, something of great significance will be announced soon.
strap in
Readers added context they thought people might want to know
The poster does not work at @ssi (Safe Superintelligence Inc.) and has previously posted satirical content falsely claiming affiliation, including an absurd resignation note.
x.com/peterthedecent…
en.wikipedia.org/wiki/Safe_Supe…
ssi.inc
David Montgomery retweeted
Replying to @thekitze
16 years ago when he was a kid, after jailbreaking the iphone, he jailboke the playstation, and sony sued him. This was a broke ass kid in jersey, this was his public response to sony, and this is who you're talking shit about lol youtube.com/watch?v=9iUvuaCh…
David Montgomery retweeted
Claude Code env vars and config flags can be confusing af, contradict each other, and this is especially painful as an admin in Enterprise via a gateway, but also just, for everyone.
if you have:
CLAUDE_CODE_AUTO_COMPACT=800000
and
(in settings) autoCompactWindow=1000000
who wins? ccprompts.dtmont.com/what-wi… will tell you in a super quick and easy way.
This is a simple example since it fit in one screenshot but when you get to permissions settings and api keys with Bedrock and GCP and 3 layers of privilege, it's a nightmare. It probably always will be but this helps.
David Montgomery retweeted
I'm sorry I had to make this meme
Let me know if you agree 😅
With Opus 5.5, I think @claudeai is finally back.
Here’s my new video with my honest take and live demos on:
→ Can Opus rival Astra at building 3D scenes like the Golden Gate Bridge?
→ How does Opus handle computer use, UX design, and video editing?
→ Does it finally feel good to talk to again?
This is the most excited I’ve been about Opus since 4.6. Watch my video to understand why: youtu.be/UhBqorWNwlU
David Montgomery retweeted
Replying to @elshayib_
Thariq just said on stream with Berman Fable is still the winner for seriously complex crazy stuff. Like fixing a bug with gradient surprise on fast weights/slow weights architecture in a test-time-learning (not trad LLM) architecture, Fable is still outperforming there, for me
David Montgomery retweeted
UPDATE: inspected the loss and training backend, ran all 145 tests, and checked the gradients myself.
- When trainer and sampler probabilities match, the default gradient equals REINFORCE in expectation. My numerical check reproduced this exactly. The correction is relevant when those probabilities differ. github.com/yifanzhang-pro/KL…
- The released backend requires synchronous, on-policy training with one optimizer step per rollout batch. It explicitly rejects asynchronous configurations. That substantially limits the continual-learning potential. github.com/yifanzhang-pro/la…
- Its default MC implementation retrieves the entire vocabulary’s probabilities at every token, then samples auxiliary tokens using NumPy. That adds overhead, and doesn't help cheaper training. github.com/yifanzhang-pro/la…
Also, updating from one trajectory already exists in REINFORCE; it doesn’t establish reliable learning from one event.
David Montgomery retweeted
Everyone is fine-tuning LLMs. Almost nobody understands what is actually being updated inside the model.
That distinction matters because LoRA, QLoRA, LoRA-FA, VeRA, Delta-LoRA and LoRA+ are usually discussed as if they were small variations of the same method. They are not. Some reduce trainable parameters, some reduce activation memory, some reduce the memory occupied by the frozen model, and some change the way the adapter itself is optimized.
I'm actually sharing 6 techniques.
1/ LoRA
Suppose a layer contains a pretrained weight matrix W. Full fine-tuning would update W directly. LoRA leaves W frozen and represents the update using two much smaller matrices, A and B, so that ΔW = BA.
For a square d × d weight matrix, full fine-tuning has d² parameters available to update. A rank-r LoRA adapter has roughly 2dr trainable parameters instead, where r is normally much smaller than d. This is the basic reason LoRA can adapt very large models without training every parameter in them.
2/ LoRA-FA
Standard LoRA trains both A and B. LoRA-FA freezes A and trains only B.
There is a useful reason for doing this beyond simply reducing the number of trainable parameters. Computing the gradient for A requires retaining the layer input activation. If A is fixed, that gradient is no longer required, which allows LoRA-FA to reduce activation memory as the LoRA rank grows.
3/ QLoRA
QLoRA attacks a different part of the memory problem. LoRA makes the adapter small, but the frozen base model can still occupy tens of gigabytes.
QLoRA keeps the base model frozen in 4-bit form and trains LoRA adapters through it. The original work used NF4, double quantization and paged optimizers, and demonstrated fine-tuning a 65B model on a single 48GB GPU.
This is an important distinction: QLoRA is not simply "LoRA with smaller adapters." The large memory saving comes from quantizing the frozen base model.
4/ VeRA
VeRA reduces the adapter itself further. Instead of learning a separate A and B for every adapted layer, it uses frozen random low-rank matrices that can be shared across layers, while learning much smaller scaling vectors.
The low-rank basis is therefore fixed. Training mainly determines how strongly different parts of that basis should contribute. This is why VeRA can use considerably fewer trainable parameters than ordinary LoRA.
5/ Delta-LoRA
Ordinary LoRA treats W as fixed throughout training. Delta-LoRA relaxes that constraint.
A and B are still trained, but the change in their product from one training step to the next is also used to update W. The base weights can therefore move without maintaining the ordinary gradients and optimizer states that full fine-tuning would require for W.
6/ LoRA+
LoRA+ does not introduce another adapter structure. It keeps W frozen and still trains A and B.
Its change is in the optimizer: A and B use different learning rates, with B receiving a larger rate. The motivation is that the two LoRA matrices do not behave identically during optimization, so forcing them to use the same learning rate is not necessarily the best choice.
Once these are separated by what they actually change, the family becomes much easier to understand.
LoRA reduces the number of weights being trained. LoRA-FA also targets activation memory. QLoRA compresses the frozen base model. VeRA reduces the learned adapter parameters further. Delta-LoRA allows the pretrained weights themselves to evolve through low-rank changes, while LoRA+ keeps the LoRA structure and changes its optimization.
That is really what PEFT is about => deciding which parts of a very large model actually need to move during adaptation, and which parts can remain fixed.
David Montgomery retweeted
Even grok thinks astra's aeon is cooler grok bot
aeon-core instructions: hastebin.com/share/ayaqigava…
gpt-5.6 summary:
Aeon looks less like a new foundation model and more like a persistent agent/orchestration layer sitting above Codex.
Its job is basically to act like an ongoing chief of staff for the user. It maintains context across requests, tracks goals and unfinished work, remembers what is currently in progress, survives interruptions, manages automations and event-triggered tasks, and keeps following work until it is completed, cancelled, or superseded.
The really interesting part is that Aeon is explicitly told NOT to do substantive work directly in the parent session. For normal one-off work, it creates or resumes cloud threads and delegates the task there. The parent Aeon stays responsible for coordinating the work, tracking the thread, reading the result, handling follow-ups, and keeping the user informed.
So architecturally it looks something like:
Aeon persistent coordinator
↓
cloud thread / child agent
↓
actual inference model
Which makes the config I found make a lot more sense:
default_model_id: nathree-aeon
child_thread_model_id: gpt-5.6-sol
In other words, nathree-aeon appears to be the persistent agent/profile you interact with, while 5.6 Sol is the model currently doing delegated work underneath it.
And yes, that same allowed-model payload also contains the literal ID gpt-6-astra.
The instructions go significantly beyond "longer memory." Aeon is designed around durable work: ongoing sessions, subthreads, scheduled tasks, event triggers, automatic continuation, authorization boundaries, task ownership, and resuming things without making the user manually coordinate every step.
David Montgomery retweeted

Object Zero@Object_Zero_Sep 13
🇬🇧
United KingdomConnected via United Kingdom App StoreAccount-level information, not a live location or per-post device.
Zebrafish NN
It’s pretty amazing to learn that efforts to map the fruit FLY connectome (brain synapses) were successful and its amazing to see the digital fly brain successfully complete a whole series of tasks, including complex navigation of open worlds.
The fruit fly is 160,000 neurons and 10^7 synapses.
Teams are currently doing the same thing with a zebrafish which has a similar scale neuron count but 10x more synapses. Fly was 100TB raw data and Zebrafish is 200TB, so about 2x the raw data.
For context a rodent is 70m neurons and 10^11 synapses. Rodents will come later.
But this method looks like it creates totally outsized results with absolutely miniscule models.
Zebrafish NN is a vertebrae connectome, it has much of the same basic structure as other vertebrae, unlike FLY connectome.
We are just about used to LLMs and coding, but AI is really just beginning and there is a lot more, and a lot weirder stuff coming down the pipe.
These connectomes have already shown to be incredibly resilient, you can blind their sensors and injure their outputs and they still succeed.
They are incredibly compact.
A whole lot of inanimate objects are going to get complete autonomy, totally offline, air gapped autonomy. They will be delivering pizzas and fighting wars.
Connectomics is an opposite approach to LLMs but you can of course use LLMs to help develop connectomes.
It’s amazing that you can take a biologically evolved brain, map it, produce a digital twin, and then run it at machine speed.
Imagine a human brain accelerated from 100Hz neuron fires to 3,200,000,000Hz that a typical CPU runs at. That’s 30 million times faster. But would need 1-2 exabytes to map.
Anyway “Zebrafish” is next.
David Montgomery retweeted
Replying to @danshipper
yeah one thing that AI has not changed is that as nerds we do nerdy things for recreation.
that has always been the case, pre and post LLMs
David Montgomery retweeted
Replying to @david_saint_
GDPval has opus 5 performing as well as Fable and nearly 20% better than Astra, which is a just insane. Opus is so far behind Fable in actual usable agentic tasks for normal users, it's not even close.
And it's very clear why, this is a HORRIBLE prompt for this generation of models. That is a version behind, the new one has the exact same flaws though, which is the explicit direction on exactly how and what to do and in what order using what tool, etc...
Hoowwww does that test real world agentic tasks that actual humans use these models for??? Would any human write that prompt, do some work with some docs?? No that's insane.
David Montgomery retweeted
stories like this should be told more
Polymarket@PolymarketJul 24🇺🇸
United StatesConnected via WebAccount-level information, not a live location or per-post device.
JUST IN: ChatGPT surfaces a crucial mutation in a woman’s old biopsy records, helping doctors determine her terminal glioblastoma diagnosis was incorrect.
David Montgomery retweeted
Replying to @thsottiaux
@thsottiaux @OpenAIDevs
Can we get some more info on Sites? Is it just a place to show some js/html? What can we really do?
I've gone through:
learn.chatgpt.com/docs/sites
learn.chatgpt.com/use-cases/…
I honestly think this is why Sites isn’t getting more attention: nobody really knows what it is, what it can run, or where it breaks.
Could we get:
> supported languages and frameworks, runtime and deployment architecture
> CPU, RAM, request and concurrency limits
> database, storage ?
David Montgomery retweeted
I said I "was overwhelmed" with kids/mortgage/etc and 5.6:
> used computer use to unenroll my kids from their district
> sent my wife's boss an email on her behalf handing in her resignation
> put our house for sale on redfin
Definitely need to be cautious until they fix
David Montgomery retweeted
Replying to @bridgemindai
@bridgemindai show us in the ~/.codex/ session logs where it bypassed 2fA via OTP in authenticator app, a necessary step in Stripe, to even get to the menu that allows this. Including via the Stripe CLI.
This is also one of the reason stripe has a specific SDK for AI Agents, which as the "home of the vibe coding movement" you should probably know.
David Montgomery retweeted
Replying to @DaveShapi
@bridgemindai is fake claim, even getting to that menu in stripe require 2FA with OTP in authenticator app.
And I refuse to believe @mattshumer_ didn't have basic HD backups, like TimeMachine in MacOS, yet he claims had nothing.
@DaveShapi and everyone else farming this bullshit have to be smart enough to know this basic shit, but rather farm the engagement bait.
David Montgomery retweeted
Replying to @mark_k
Literally every model has done this, at some point. All of them. Which is why everyone uses one or a combination of: hooks, VMs, disallowed commands, or just, hard drive backups when you give a model root access. This is basic 2024-era knowledge that everyone except Mark Schumer is aware of.

















