Nikhil Singhal

CTO | VP Engineering | AI Practitioner | Builder Who Governs | Author, HIP Charter ( | Expedia, T-Mobile, Microsoft

[Nikhil Singhal @nikhilsinghal]

@ClaudeDevs @trq212 The stupidity of fable. I was talking about my son who is studying biology at UCSD. And fable flips to opus 4.8 because it got triggered by word biology.

Fable is lobotomized. Thank you for the crappy experience

[Nikhil Singhal @nikhilsinghal]

@bcherny @elonmusk I would really really like this to work. It will be a dream come true

[Nikhil Singhal @nikhilsinghal]

@elonmusk Would this work without the supergrok mode?

[Nikhil Singhal @nikhilsinghal]

@AnthropicAI No wonder Opus 4.8 is totally useless and is spewing junk today

[Nikhil Singhal @nikhilsinghal]

Have tried yet but on my list

[ClaudeDevs @ClaudeDevs]

We’ve shipped a security-guidance plugin for Claude Code that helps identify and fix vulnerabilities as you’re writing code.

Available for all Claude Code users. Install from the plugin marketplace (/plugins).

[Nikhil Singhal @nikhilsinghal]

If you are working in an enterprise level code base, this article should be a must read. It will save you days of pain and frustration. I personally learnt about LSP which I was missing in my implementations

[ClaudeDevs @ClaudeDevs]

What are best practices for running Claude Code at scale?

New blog post on what we've learned from teams running it across multi-million-line monorepos, decades-old legacy systems, and distributed microservices:

https://t.co/rJUYlIUiTT

[Nikhil Singhal @nikhilsinghal]

What a shit show

[Garry Tan @garrytan]

Sanders and AOC introduced a bill to pause ALL AI data center construction. 300+ local bills filed. Half of planned 2026 data centers facing delays or cancellation. Each one brings billions to local economies.

The people who say they want American jobs are trying to block the biggest job creation engine since the interstate highway system.

[Nikhil Singhal @nikhilsinghal]

@eng_khairallah1 Honest truth? Stop generating AI slop. Give it your voice

[Nikhil Singhal @nikhilsinghal]

@ihtesham2005 Dude. Stop using Claude to write your posts. Just a cursory check shows this is pure AI slop. Do a little effort

[Nikhil Singhal @nikhilsinghal]

I would add MCP’s and Agents to this list as first class items enterprise’s and its users are very excited about

[JJ Englert @JJEnglert]

10 things I'm seeing on the frontlines of AI adoption in the enterprise:

1. Chat is where 90% of employees still live. It's the gateway drug. Everything else is downstream of getting people comfortable here first.

2. Power users discover Cowork and lose their minds. It's the "wait, it can actually do the work?" moment.

3. Claude Code has very little penetration with non-technical users in the enterprise still.

4. Microsoft being the "approved" tool doesn't matter. Employees route around Copilot and pitch their managers for Claude access on their own.

5. Artifacts in Claude are a breakout feature. People don't want to view them — they want to deploy them, connect them to Snowflake, etc., ship them as internal MVPs for their org to actually use.

6. Cowork is crossing the line from "demo" to "real work." Legal teams redlining contracts. Ops teams running workflows. Then immediately asking: how do I automate this for production?

7. The next unlock → automated cloud workflows that leverage an agent like Claude while keeping non-technical users within the tools they're already using and in a chat interface. The demand is screaming.

8. Terminology is major blocker. Projects vs. skills vs. plugins vs. agents. I've explained "what is a skill" 200+ times. The moment it clicks, people get excited — but the path there is too long.

9. Enterprise IT restrictions (locked connectors, no browser access) quietly strip Cowork of its superpowers. The features that make it magical are the first ones IT disables.

10. There is a high level of "AI insecurity". For the first time in a long time, people at all levels (even C-Suite) need to signifcantly upskill in order to stay world class in their positions, and this is causing people to be insecure about their skill set across the org.

General note on Microsoft: I spent a lot of this past week deep in Power Automate and Copilot Studio trying to build an automated solution in the cloud — given it's the native tool with sanctioned access to their org's data.

It's ~90% there. But the final 10% is riddled with terrible UX, inconsistent behavior, and a generally poor experience.

Honestly feels like Microsoft is fumbling the biggest moment in their company's history with software that has all the features on paper but lacks the magical "just works" moment for non-technical team members. The gap is wide open and they're letting others
"eat their lunch" right now.

[Nikhil Singhal @nikhilsinghal]

@sukh_saroy This is so Claude written. At least take some time to fix the AI tell tales from your post

[Nikhil Singhal @nikhilsinghal]

@ShahRathin has compiled the GOLD standard, a blueprint, a guidebook, a playbook for startups to come in future. I wish I had this when I was doing startups.

Kudos

[Rathin Shah @ShahRathin]

https://t.co/ba6mgOyedQ

[Nikhil Singhal @nikhilsinghal]

Wow. @lennysan has done an amazing job of listing the biggest takeaways.

[Lenny Rachitsky @lennysan]

My biggest takeaways from Claude Code's Head of Product @_catwu:

1. Anthropic’s product development timelines have gone from six months to one month, sometimes one week, sometimes one day. Part of this acceleration is access to the latest models (i.e. Mythos). Another is shipping new products into “research preview,” making clear it's early, experimental, and might not be supported forever. Another is an evergreen "launch room "where engineers post ready features and marketing turns around announcements the next day.

2. The PM role is shifting from coordinating multi-month roadmaps to enabling teams to ship daily. As Cat puts it, “There should be less emphasis on making sure you are aligning your multi-quarter roadmaps with your partner teams and more emphasis on, OK, how can we figure out the fastest way to get something out the door?”

3. The most efficient shipping unit is an engineer with great product taste. On Cat’s team, many engineers go end-to-end—from seeing user feedback on Twitter to shipping a product by the end of the week—without a PM involved. Also, almost all the PMs on the Claude Code team have either been engineers or ship code themselves, and the designers have been front-end engineers. The roles are merging, and the most valuable skill is product taste, not job title.

4. Build products that are on the edge of working. Claude Code’s code review product failed multiple times because earlier models weren’t accurate enough. But because the prototype was already built, they could swap in Opus 4.5 and 4.6 and immediately test whether the gap was closed. Teams that wait for the model to be ready will always be a cycle behind.

5. The most underrated skill for building AI products is asking the model to introspect on its own mistakes. Cat regularly asks the model why it made an unexpected decision. The model will explain that something in the system prompt was confusing, or that it delegated verification to a subagent that didn’t check its work. This reveals what misled the model so the team can fix the harness.

6. Every model release forces their team to revisit existing products and audit their system prompt to remove features the model no longer needs. Claude Code’s to-do list was a crutch for earlier models that couldn’t track their own work. With Opus 4, the model handles it natively. Features built as scaffolding for weaker models become debt when the model catches up—so the team actively strips them.

7. Anthropic employees build custom internal tools instead of buying SaaS products. A sales team member built a web app that pulls from Salesforce, Gong, and call notes to auto-customize pitch decks—work that used to take 20 to 30 minutes now takes seconds. Their core stack is Claude Code, Cowork, and Slack. No Notion, no Linear, no Figma.

8. People underestimate how much Claude’s personality contributes to its success. As Cat describes it, “When you reflect on everyone you’ve worked with, there’s just some people where you’re like, I really like their energy, their vibe.” Claude is designed to be low-ego, positive, competent, and earnest—qualities that make it feel like a great coworker, not just a tool. This isn’t cosmetic; it’s what makes people want to use Claude for hours every day. The team has a dedicated person, Amanda, who “molds Claude’s character,” and it’s one of the hardest roles at the company because success is so subjective.

9. The future of work is managing fleets of AI agents, not doing the work yourself. Cat sees a clear progression: first, individual tasks become successful. Then people start running multiple tasks at the same time (multi-Clauding). Next, people will run 50 or 100 tasks simultaneously, which will require new infrastructure—remote execution, better interfaces for managing tasks, agents that fully verify their work, and self-improving systems that incorporate feedback. The human role shifts from doing the work to knowing which tasks to look into, verifying outputs, and giving feedback that makes the system better over time.

10. Hire people who lean into chaos and face every challenge with a smile. At Anthropic, there are weeks when a P0 on Sunday becomes a P00 by Monday and a P000 by Monday afternoon. If you get too stressed about any one thing, you’ll burn out. Their team looks for people who can look at a hard challenge and say, “Wow, that’s gonna be hard. But I’m excited to tackle it and I’m gonna do the best that I possibly can.” This mindset—optimism, resilience, and comfort with constant change—is increasingly essential as the pace of AI development accelerates.

Don't miss the full conversation: https://t.co/1wOUHcdYQN

[Nikhil Singhal @nikhilsinghal]

@OfficialLoganK @GoogleAIStudio RIP your DMs

[Nikhil Singhal @nikhilsinghal]

I need someone to build me an extension or plugin or something that can take a post on X and generate an md file or pdf or something that I can then share with Claude. This is ridiculous

[Nikhil Singhal @nikhilsinghal]

@felixrieseberg @bcherny The problem of posting only on X is that my Claude web or code cannot check this. I have to jump through the hoops to get this to them. Do you also post on Anthropic blog? @felixrieseberg

[Nikhil Singhal @nikhilsinghal]

Context degrades, summaries drift, and the AI quietly forgets things you never asked it to forget. I thought I understood the problem well. Then I read this piece by Chrys Bader and realized I was only seeing half of it. He frames memory as an unsolved spectrum between raw (lossless but inert) and derived (compact but drifting like a photocopy of a photocopy). Every memory system is choosing a position on that spectrum, and neither extreme works. Best thing I have read on this topic.

[Chrys Bader @chrysb]

https://t.co/dPP9HPvML2

[Nikhil Singhal @nikhilsinghal]

I am an early adopter and loving the convenience this is bringing to my work

[Claude @claudeai]

You can now enable Claude to use your computer to complete tasks.

It opens your apps, navigates your browser, fills in spreadsheets—anything you'd do sitting at your desk.

Research preview in Claude Cowork and Claude Code, macOS only.

[Nikhil Singhal @nikhilsinghal]

My three AI's don't talk to each other.

Grok lives in my Tesla. Perfect voice, native to the car, always listening. I ask it about traffic, markets, news. It is fast and sharp. But it knows nothing about me.

Copilot lives in my work. Documents, email, meetings, code. It understands my files and my calendar. But it has no idea what I am building on my own time or what I care about outside of work.

Claude lives in my personal projects. It knows my family. It knows the trademark I filed this week. It knows the book I am writing, the stories I have been collecting for months, and the repos where all of it lives. When my wife made an observation from the driver's seat today, the AI connected it to a theme we had been developing for weeks.

Three extraordinary tools. Three completely isolated worlds.

This afternoon, I spent 45 minutes in the passenger seat of my Tesla, talking to my phone instead of talking to my car, because the AI that knows my work lives on a mobile app and the one built into the dashboard does not know me. The AI that could have connected it to my work calendar was somewhere in the cloud. None of them could see what the others were doing.

We have been so focused on making AI more capable that we forgot to make it more continuous.

The next breakthrough is not a smarter model. It is an AI that remembers you, no matter where you talk to it.

@elonmusk @DarioAmodei