You should just put /goal and a mildly sensible prompt and have multiple agents working on their own goals.
It removes the hassle of back-n-forth responding to the agents and also provides you enough freedom to actually think and not just be an enabler of systems (yes/no) for your agents.
You can't even use the codex subscription for your own usecases now.
this is why we should have more frontier open-weight models
156 Indian government websites are currently inaccessible because of a cert revocation by @eMudhra, including 4 that come under @GoI_MeitY. One of them is @ccaindiapki - which regulates eMudhra.
cc @internetfreedom
I made a list: captnemo.in/blog/2026/10/23/…
Replying to @GoI_MeitY
The reported security incident pertains to this only. MeitY is not involved in its audit.
The impact of this incident on Indian websites and applications have been very limited and for a very short interval.
This will be one hell of an RCA report, the beginning of the agentic era postmortem format. Going to have a lot of learnings
Neoclouds will get resilient.
Folks have no idea how giants like AWS/GCP have had mammoth security issues pre-AI era and they came through with battle scars. All because of putting security foremost everything else.
I just read how Railway moved on from using the gcp managed KMS for storing the encryption keys to their own to lower down costs, and how it come to bite them now. But they are the only ones who have been transparent about how they operate in their engineering blogs. I found next to nothing on Fly or vercel
its time the industry shifted to epehemeral passkeys that auto-rotate at half-life instead of static api keys
An urgent notice from the Railway team
blog.railway.com/p/security-…


















