kannav

too busy jumping into rabbit holes

[kannav @Kannav02]

“you’re not slopping hard enough” might unironically be the best advice I’ve heard all week

[Theo - t3.gg @theo]

I think all developers need to read less code. I know this is a hot take, but I think you'll agree if you listen.

[kannav @Kannav02]

@tibor_tee congrats tee!🎉

[kannav @Kannav02]

@fallinfromyou yeah right!

[kannav @Kannav02]

It’s been nearly two months since I last wrote a blog lol. Went for a walk yesterday, grabbed a cup of tea, and somehow started connecting ideas from books, blog posts, and things I’ve read on X over the past month or so.

I think I might have a really good blog to share soon.

[Claude @claudeai]

Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits.

Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit.

Demand for Fable has been challenging to predict, which is why we rolled it out to subscription plans in stages, extending access several times as we secured additional capacity.

[Alex Ker 🔭 @thealexker]

underrated gems in Kimi-K3 release:

> an early K3 wrote the majority of the kernels in the late development stages
> it built a triton-class compiler from scratch, MiniTriton, that delivers performance on par with or better than Triton and torch.compile
> then it designed a chip, by a model, for a model, in one 48-hour autonomous run

the model is rewriting and optimizing every layer of the stack it runs on: kernels for its own training. A compiler for its own kernels. silicon for its own weights.

we're watching software build its own hardware

[kannav @Kannav02]

finished reading how self consistency inference technique works with top-p sampling, implemented some examples with qwen 3 0.6B model, saw the difference in responses, but i think its much more visible with models having more params

[kannav @Kannav02]

@sarahfim I have a custom implementation of /bug-to-lint skill that I originally found through one of @dhasandev ‘s blog, every repo/product i’m working on has some serious linting rules now lol

P.S i’ve found linting to also limit the blast radius from an agent

[kannav @Kannav02]

975B-parameter MoE (41B active) model with native multimodal support, damn, thats nice

[Thinking Machines @thinkymachines]

Today, we are introducing Inkling.

Inkling reasons efficiently across text, image, and audio modalities. We are making the full weights available.

https://t.co/Ghebq5mG30

Available today for fine-tuning on Tinker. Play with it in the Inkling Playground. 🧵

[Sid @sid_srk]

https://t.co/NeC6Q3Vvjp

[kannav @Kannav02]

seeing more mutuals on my tl, the algorithm is just perfect

[superwhisper @superwhisper]

The Superwhisper CLI + MCP server are here. Check out our full walkthrough on both of these new features ✨

[kannav @Kannav02]

toronto looks unreal today

[kannav @Kannav02]

@theo 2 looks clean, pretty concise about the details as well

[kannav @Kannav02]

@sid_srk 🔥🔥

[Tibo @thsottiaux]

Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice.

Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday.

We’ve spent the last 24 hours reading feedback, looking at usage patterns, and talking with many of you. The short version is that there is a *lot* of excitement for GPT 5.6 Sol, ChatGPT Work on mobile & web, but also that we didn't get everything quite right.

- We made it too easy to use the highest-compute settings without making the impact on usage limits sufficiently clear.
- We reorganized the desktop app in one bold move, making familiar things like chats and projects harder to find.
- Our launch framing was focused on ChatGPT Work and to some of our Codex fans it made it feel like Codex was going away over time. Absolutely not our intention, we love Codex and it is here to stay.
- And we introduced regressions for some existing multi-agent workflows, alongside a collection of rough edges in plugins and other parts of the experience.

We’re landing a first set of improvements today. We’re resetting usage twice so people can keep experimenting, changing defaults and the model picker so they don’t push people toward unnecessarily expensive settings, fixing several plugin submission issues, improving how we represent Codex in the product, and cleaning up some of the most immediate desktop problems.

A larger set of improvements will land next week. We’re bringing chats and projects back into the sidebar in a more familiar and customizable way, making usage and reset timing much more visible, clarifying when to use ChatGPT Work and when to use Codex, and addressing the many other smaller pieces of great feedback we've had.

The ambition behind this launch hasn’t changed. We think bringing ChatGPT and Codex together into a workspace where people and agents can collaborate is a very important step forward. But an ambitious direction doesn’t excuse avoidable confusion or regressions in the first version.

Please keep the feedback coming. We’re moving quickly, and you should see the experience already get better with a few updates today; and substantially better again next week.

[kannav @Kannav02]

Comparing reading ai generated code to reading compiler output is a baseless comparison, compiler gives verified and deterministic outputs, agent does none

[kannav @Kannav02]

@PrimeIntellect Congratulations!!! 🙌

[OpenAI @OpenAI]

GPT-5.6 Sol, along with Terra and Luna, will launch publicly this Thursday.

We’re expanding preview access globally now.