𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯

Learning Ai at the moment.

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@grok
Summarize the whats an ai agent , the fundamental idea behind it and types of ai agents .. when we say ai agents .. how many types of ai agents are there theoritically vs practically present . For ex : Clawdbot it a reAct based ai agent . Contrast and extract the info . Ai agent architechture and how can someone learn to build in real time vs cost benifit analysis of it . Which is the best platform to build these ai agents

[Elon Musk @elonmusk]

Interesting

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

Great to hear @theburntpeanut ... You're the next biggest gamer acc. to @grok :)

[Suryansh Tiwari @Suryanshti777]

Andrej Karpathy just explained the future of software engineering without directly saying it.

The best AI engineers are no longer “prompting.”

They’re building systems around the agents.

Karpathy’s biggest insight wasn’t:
“Claude can code.”

It was:
LLMs become dramatically better when you force them into disciplined workflows.

That’s why "CLAUDE.md" files are suddenly everywhere.

Not because they’re prompts.

Because they behave like an operating system for the agent.

Karpathy called out the exact problems with AI coding:

- models assume instead of asking
- they overengineer simple tasks
- they hide confusion
- they rewrite unrelated code
- they optimize for completion, not correctness

So developers started encoding rules directly into the workflow:

→ Think before coding
→ Simplicity first
→ Surgical edits only
→ Goal-driven execution

And the results are wild.

People are now running multiple Claude Code agents in parallel like engineering teams:

• one agent researching
• one debugging
• one writing tests
• one optimizing code
• one validating outputs

Not “AI assistance.”

Actual orchestration.

And this part from Karpathy changes everything:

“Don’t tell the model what to do. Give it success criteria and let it loop.”

That is the shift.

From:
“write this function”

To:
“here’s the goal, constraints, tests, and verification system — now iterate until correct.”

The craziest part?

This already feels like a phase shift in engineering.

A lot of developers quietly went from:
80% manual coding → to 80% agent-driven coding in just months.

Not because AI became perfect.

Because the leverage became impossible to ignore.

We’re entering an era where the highest leverage engineers won’t necessarily be the best coders.

They’ll be the people who build the best systems around AI agents.

[Anam Hira @anamhira]

same flow, 10 parallel runs, fresh cloud device each time. vision-based, no selectors.

if one fails, it's a real bug, not a flake.

check every PR across security, design and engineering

[Khairallah AL-Awady @eng_khairallah1]

https://t.co/eh4bTemnMx

[Unsloth AI @UnslothAI]

We collaborated with NVIDIA to teach you how we made LLM training ~25% faster! 🚀

Learn how 3 optimizations help your home GPU train models faster:
1. Packed-sequence metadata caching
2. Double-buffered checkpoint reloads
3. Faster MoE routing

Guide: https://t.co/nwvVfNC8XE

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@RoundtableSpace @grok where can i find the complete video of this ? Gimme the YT link ,

[0xMarioNawfal @RoundtableSpace]

ANTHROPIC JUST RELEASED THE OFFICIAL PLAYBOOK FOR BUILDING A COMPANY WITH CLAUDE CODE.

CEO: 1 human. Employees: AI agents. Operations: fully automatic.

The zero-headcount company is no longer a joke.

[Anatoli Kopadze @AnatoliKopadze]

https://t.co/SJ5O5tIrlT

[𝗿𝗮𝗺𝗮𝗸𝗿𝘂𝘀𝗵𝗻𝗮— 𝗲/𝗮𝗰𝗰 @techwith_ram]

𝗔 𝗧𝗶𝗺𝗲 𝗦𝗲𝗿𝗶𝗲𝘀 𝗙𝗼𝘂𝗻𝗱𝗮𝘁𝗶𝗼𝗻 𝗠𝗼𝗱𝗲𝗹 𝗕𝘆 𝗚𝗼𝗼𝗴𝗹𝗲

This has been pre-trained on a time series corpus of 100 billion data points, & shows impressive performance on various benchmarks from diverse domains.

𝗧𝗶𝗺𝗲𝘀𝗙𝗠 𝗚𝗶𝘁𝗵𝘂𝗯 𝗽𝗮𝗴𝗲: https://t.co/o5V5NWWD03
𝗟𝗲𝗮𝗿𝗻 𝗠𝗟 𝗮𝗻𝗱 𝗙𝗼𝗿𝗲𝗰𝗮𝘀𝘁𝗶𝗻𝗴: https://t.co/L8dR5mELSZ

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

Prompt Engineering 𝕏 Claude 📈

[Rahul @sairahul1]

Two Anthropic engineers spent 24 minutes exposing every Claude Code feature you didn't know existed.

Most people will scroll past this. Don't be most people.

[Guillermo Rauch @rauchg]

Here's my update to the broader community about the ongoing incident investigation. I want to give you the rundown of the situation directly.

A Vercel employee got compromised via the breach of an AI platform customer called https://t.co/7PY6gGtzgI that he was using. The details are being fully investigated.

Through a series of maneuvers that escalated from our colleague’s compromised Vercel Google Workspace account, the attacker got further access to Vercel environments.

Vercel stores all customer environment variables fully encrypted at rest. We have numerous defense-in-depth mechanisms to protect core systems and customer data. We do have a capability however to designate environment variables as “non-sensitive”. Unfortunately, the attacker got further access through their enumeration.

We believe the attacking group to be highly sophisticated and, I strongly suspect, significantly accelerated by AI. They moved with surprising velocity and in-depth understanding of Vercel.

At the moment, we believe the number of customers with security impact to be quite limited. We’ve reached out with utmost priority to the ones we have concerns about. All of our focus right now is on investigation, communication to customers, enhancement of security measures, and sanitization of our environments. We’ve deployed extensive protection measures and monitoring. We’ve analyzed our supply chain, ensuring Next.js, Turbopack, and our many open source projects remain safe for our community.

The recommendation for all Vercel customers is to follow the Security Bulletin closely (https://t.co/BLVnic9fJC). My advice to everyone is to follow the best practices of security response: secret rotation, monitoring access to your Vercel environments and linked services, and ensuring the proper use of the sensitive env variables feature.

In response to this, and to aid in the improvement of all of our customers’ security postures, we’ve already rolled out new capabilities in the dashboard, including an overview page of environment variables, and a better user interface for sensitive env var creation and management. As always, I’m totally open to your feedback.

We’re working with elite cybersecurity firms, industry peers, and law enforcement. We’ve reached out to Context to assist in understanding the full scale of the incident, in an effort to protect other organizations and the broader internet. I also want to thank the Google Mandiant team for their active engagement and assistance.

It’s my mission to turn this attack into the most formidable security response imaginable. It’s always been a top priority for me. Vercel employs some of the most dedicated security researchers and security-minded engineers in the world. I commit to keeping you updated and rolling out extensive improvements and defenses so you, our customers and community, can have the peace of mind that Vercel always has your back.

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@bryan_johnson How did u deal with Pollution in india ? You've visited recently... The way you were suffocating .. I'm feeling rn ...

Any suggestions ???? :)

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@AravSrinivas @grok is this info on the dot ?

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@AravSrinivas @grok why does he say that ?

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@PakArmyDept @realDonaldTrump Pak surrender to india .. Aap log apni dhunn me sawar ho 🤣

[Mr bajranga @Mrbajranga]

@realDonaldTrump Look at this, Prime Minister of Pakistan 🤣 India is king 👑🇮🇳

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@al_yasko Anaconda Navigator🐍

[𝖘𝖍𝖆𝖍𝖎𝖉 𝖆𝖑𝖎 ✯ @ZeusXai]

@waitin4agi_ Definitely a strong yes. AI models are becoming smarter, faster, and more precise with any given prompt. I feel like prompt engineering is an art right now, but soon it’ll become more of a skill.