Mohan Raj Sujay

Rottweiler🐾 | Tech Evangelist & Cloud aficionado 🌟 | Sharing bytes of tech wisdom 🚀

#TechEvangelist #CloudInnovator"

[OpenAI @OpenAI]

This is GPT-6 Astra.

Anything you can do on a computer, Astra can do for you. Fast.

[Claude @claudeai]

We’re introducing Claude Fable 5.1 and Claude Mythos 5.1.

They're the world’s most advanced models for coding and knowledge work.

[Mohan Raj Sujay @sujayR15]

@surim0n Toronto

[Claude @claudeai]

Introducing Claude Science, a new app designed with every stage of research in mind.

Artifacts traced to their code, environments managed on demand, and 60+ optional scientific databases that you can connect.

Available now in beta.

[Claude @claudeai]

Introducing Claude Sonnet 5, our most agentic Sonnet yet.

It makes plans, uses tools like browsers and terminals, and runs autonomously at a level that just a few months ago required larger and more expensive models.

[Sakana AI @SakanaAILabs]

Introducing Sakana Fugu: A full multi-agent orchestration system accessible via a single model API.

Our ‘Fugu Ultra’ model matches the performance of Fable and Mythos, delivering frontier capability without the risk of export controls.

Try it: https://t.co/hhO6qTawgb 🐡

[Claude @claudeai]

Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use.

Its capabilities exceed those of any model we’ve ever made generally available.

[Claude @claudeai]

We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity.

This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.

[SpaceX @SpaceX]

SpaceXAI and @cursor_ai are now working closely together to create the world’s best coding and knowledge work AI.

The combination of Cursor’s leading product and distribution to expert software engineers with SpaceX’s million H100 equivalent Colossus training supercomputer will allow us to build the world’s most useful models.

Cursor has also given SpaceX the right to acquire Cursor later this year for $60 billion or pay $10 billion for our work together.

[Mohan Raj Sujay @sujayR15]

GPT-5 has 1 trillion+ parameters. This post starts with 1.
Just published — Understanding LLM — Part 1

https://t.co/28NfDBAJHr

#AI #LLM #MachineLearning #Python #NLP

[jack @jack]

https://t.co/jgZkBvYOPt

[shawn @shawnbuilds]

80 people showed up to 🇨🇦 Build Canada Hackathon with Cursor, let's go!

[Feross @feross]

🚨 CRITICAL: Active supply chain attack on axios -- one of npm's most depended-on packages.

The latest [email protected] now pulls in [email protected], a package that did not exist before today. This is a live compromise.

This is textbook supply chain installer malware. axios has 100M+ weekly downloads. Every npm install pulling the latest version is potentially compromised right now.

Socket AI analysis confirms this is malware. plain-crypto-js is an obfuscated dropper/loader that:

• Deobfuscates embedded payloads and operational strings at runtime
• Dynamically loads fs, os, and execSync to evade static analysis
• Executes decoded shell commands
• Stages and copies payload files into OS temp and Windows ProgramData directories
• Deletes and renames artifacts post-execution to destroy forensic evidence

If you use axios, pin your version immediately and audit your lockfiles. Do not upgrade.

[Andrej Karpathy @karpathy]

Software horror: litellm PyPI supply chain attack.

Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.

LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.

Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.

Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.

Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.

[Animesh Koratana @akoratana]

Introducing: PlayerZero

The world's first Engineering World Model that puts debugging, fixing, and testing your code on autopilot.

We've raised $20M from Foundation Capital, @matei_zaharia (Databricks), @pbailis (Workday), @rauchg (Vercel), @zoink (Figma), @drewhouston (Dropbox), and more

PlayerZero frees up 30% of your engineering bandwidth by:
1.⁠ ⁠Finding the root cause for bugs & incidents in minutes that engineering teams take days to identify.
2.⁠ ⁠Predicting in minutes, edge case issues that a 300-person QA team would take weeks to find.

------

Here's why this matters:

No one in your org has a complete picture of how your production software actually behaves.

Support sees tickets. SRE sees infra. Dev sees code. Each team builds their own fragmented view - and none of these systems talk to each other. When something breaks, everyone scrambles to stitch the picture together by hand.

PlayerZero connects all of it into a single context graph -

→ The Slack thread where your lead said "we went with X because Y fell apart in prod last time"
→ The PR review where an engineer explained the tradeoff
→ The lifetime history of your CI/CD pipeline, observability stack, incidents, and support tickets

So you can trace any problem to its root cause across every silo.

And it compounds. Every incident diagnosed teaches the model something new. The longer it runs, the deeper it understands - which code paths are high-risk, which configurations are fragile, which changes tend to break which customer flows.

So when you sit down to debug a live issue, you have your entire org's collective reasoning and production memory behind you - instantly.

------

Zuora, Georgia-Pacific, and Nylas have reduced resolution time by 90% and caught 95% of breaking changes and freeing an average of $30M in engineering bandwidth.

------

Our guarantee:

If we can't increase your engineering bandwidth by at least 20% within one week, we'll donate $10,000 to an open-source project of your choice.

Book a demo - https://t.co/dH1dulIwSS

[Tesla @Tesla]

Announcing TERAFAB: the next step towards becoming a galactic civilization https://t.co/IDKey07mJa

[Mohan Raj Sujay @sujayR15]

@benln ✋

[Mohan Raj Sujay @sujayR15]

Redis - Back to OpenSource

#redis #opensource https://t.co/A1oJO1IEQO

[Sam Altman @sama]

what's happening with ai adoption in india right now is amazing to watch.

we love to see the explosion of creativity--india is outpacing the world.

[Mohan Raj Sujay @sujayR15]

Another vulnerability
#IngressNightmare

https://t.co/KKZsbiMVsn