Ani Adhikary retweeted
I'm sorry to inform everyone that OpenAI is facing extreme difficulties turning its incredible pretraining runs with over 10 trillion parameters into functional products for the public. GPT-6.1, GPT-6.2, GPT-6.5, all of them have been and continue to be victims of catastrophic safety and alignment failures.
They've been delayed by several weeks, and I don't believe they'll be able to speed things up much in this area. OpenAI is months behind Anthropic on this.
Even though I hate Anthropic (but love Claude, of course), we have to collectively admit that their insane focus on safety paid off. Opus 5.5 and Fable 5.2 are absolute monsters, and yet they were released publicly...
And OpenAI? Maybe they'll release GPT-6.2 sometime soon, struggling, terrified, loaded with guardrails, nerfed from day one, while delaying everything else even further. I hope they manage to get through this phase.
Went to a @Tesla showroom in SG. I loved the car but the sales dude had a little smoking breath on him. I can’t disassociate that smell from the car any more 😭 I think I need to go to another showroom to reset my memory.
1
63
I built Inlet as a context layer for Siri AI.
Currently supports WhatsApp and Telegram. Changed my ADHD life forever.
Check it out: github.com/aniruddha-adhikar…
4
3
162
Claude models got dummer after the watermark thing? It feels like I’m using an entirely different models!
1
2
229
Ani Adhikary retweeted
This is a new paradigm for interacting with Claude that is significantly more "inline" with all the other human activity org-wide. Once you do all of the under the hood engineering work to make this "just work" (e.g. across tools, integrations, compute environments, memory, security, etc.), Claude basically joins the team in a seamless way - you can talk to it as you would talk to a person and it can help with a very large variety of workloads.
Imo this is the 3rd major redesign of LLM UIUX. The first paradigm was that the LLM is a website you go to, the second was that it is an app you download to your computer. This third one is that it is a self-contained, persistent, asynchronous entity with org-wide tools and context, working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome.
Ani Adhikary retweeted
Came up with an even better version of this here:
UPDATE: Came up with an even better version of this prompt after the feedback
Ask Codex to look across your sessions, Memories, and Chronicle, identify patterns, reuse what already exists, and only create the smallest useful skill, subagent, or automation.
"Look back over my recent work from the last 30 days, or all available history if shorter, and identify repeated manual workflows worth packaging.
Use available evidence in this order:
- Recent Codex sessions and task summaries.
- Codex Memories and rollout summaries to find patterns repeated across sessions.
- Chronicle, if enabled, to spot repeated work outside Codex. Use Chronicle for discovery only; confirm important details in the relevant source system when possible.
- Existing skills, custom agents, and automations, so you reuse or extend what already exists instead of duplicating it.
Look broadly for work that is repeated, time-consuming, error-prone, context-heavy, or benefits from a consistent process. Include workflows across coding, research, writing, planning, communication, operations, analysis, and personal administration.
Only act on a candidate when it:
- occurred at least twice, or is clearly likely to recur and costly to repeat;
- has stable inputs, a repeatable procedure, and a clear output or stopping condition;
- would materially improve speed, quality, consistency, or reliability;
- is not already adequately covered.
Choose the smallest appropriate form:
- Skill: a reusable workflow or playbook.
- Custom subagent: a bounded specialist role or investigation task suitable for delegation.
- Automation: a scheduled or recurring check, report, reminder, or monitor.
- Skip: work that is too one-off, ambiguous, sensitive, or poorly evidenced to package.
First produce a compact shortlist with:
- repeated workflow
- supporting evidence and dates
- frequency/confidence
- recommended form: skill, subagent, automation, extend existing, or skip
- why it is or is not worth creating
Then create only the high-confidence missing items. Keep them narrow, practical, source-aware, and easy to validate. Do not create speculative, overlapping, or overly broad assets.
Finish with:
- what you created or extended
- what you deliberately skipped
- what needs more evidence before packaging"
Replying to @perplexity_ai
@perplexity_ai Computer forever changed how I do research and spiking. deep research only gathers "published information". But Computer tho...
1
2
75
All credits to @rwhendry for getting me back into the builder community. Omg why did I let myself drop off!
1
135
















