I really like how you pointed out that serial time is the priority and not a secondary thought in between agent work. This is my key takeaway from your article. You can design a lot upfront let the agent go. Then, dedicate your best hours to ensure that the agent output is aligned with your expectation.
Re cognitive debt - I've been saying the same for a while. I have colleagues who can run 4+ agents and keep up with them and still produce code that they intuitively understand. I personally can manage with 2 agents and some background tasks.
Part of my architecture is also having a hypothesis of what the output should be and what modules are being changed. This helps me keep an up to date understand of the system.
this is freaking insane. the applications of this will kill custom skills, system prompts, memories etc. you can have a second brain programmed with your experience and knowledge. deployment will be a scaling problem but each user can have their own LLM weight-programmed to fit their specific needs.
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math.
It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training.
We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵
Blog: https://t.co/bOWCcFhCVq
We asked GPT-6 Astra to edit Qwen3.5-0.8B weights to improve math.
It directly changed only 0.016% of weights, fixing 0.8B's reasoning loops & improving math up to 6x and even instruction following 3x, without gradients or training.
We call this Weight-Space Programming: frontier LLMs can now natively read/write neural network weights! 🧵
Blog: https://t.co/bOWCcFhCVq