Sub Agentic Swarm
Your team of agents has agents who have sub agents. Chris Nolan will be so happy.
With the introduction of Agent Teams
Random Corners of the internet
OpenAI launched GPT-5.3 Codex this monday [link] and Anthropic (finally) launched its Opus 4.6 [link] within a week.
Almost feels like iOS v/s Android ecosystem Déjà vu.
Elon finally reveals his actual reason for buying twitter (X or whatever he fancies). [link] He is just one step away from the Cyber-ia world he envisions. Asking for a friend (Tesla), what does SpaceX cost?
Moltbook is a ‘view only’ experience for all humans - that can prompt their AI agents and connect it to the AI agents only social media platform. Dystopia, we there yet?
Social media starts buzzing with ‘It was never one lab that would reach AGI, It was always millions of AI agents interacting.” Doomers have a field day. Gloomers are crying tears of joy. Where’s the firm but kind hand of the lord now!?
OpenClaw, Clawdbot or whatever fancies your tushy, as long as Dario doesn’t hear about it, leaks meaty sensitive data of its agentic owners. Even Andrej Karapathy is a victim [link].
Personal Experiences
The Claude Code Loop that everyone has experienced by now.
I created a docker compose file back in 2023 to emulate Azure Cosmos database. For fun, in 2026, asked Claude to better the docker compose file. And it jumped right into action. A separate disk for working memory, storage, and even regular health checks. Only problem was, after spinning up the docker container, nothing worked.
We have all been there. You try something small and hope AI magic delivers Principal Software Engineer level code (as promised by the AI gloomers) and get stuck in a loop of it trying to establish the goal.
In my case, the addition of disks, creating folders etc. was running into permissions issues. Claude adds user: root to the file. Viola, postgres stops working in the background. (I find it funny that cosmos does not use MSSQL).
Next, it stops going in this direction and starts hammering my server to check every 5 seconds for at least 25 attempts, because Claude believes the CosmosDB was never ready in the first place.
Finally, Claude, after at least 20 tries at this problem, wrongly concludes that it is not possible to emulate Azure Cosmos on device. It recommends switching to either a free version or a testing / staging database.
After an eternity, I finally send the original docker file and tell it, this worked. I get the much deserved apology.
The apology:
You are right, I am sorry for overcomplicating it. Does the cosmos-db-emulator container work now?
And this was before I even attempted adding a testing agent to my system.
Welp. That’s it for today. See you around.
