Joined March 2026
Dan Gora retweeted
The team and I use Auto mode exclusively, and have been for many months. I couldn't imagine going back to permission prompts! Really excited to get this out to everyone.
Starting August 14, auto mode will be the default permission mode in Claude Code for Pro, Max, and Team users. Auto mode reviews shell commands and actions with a separate classifier. In testing, it caught 89% of dangerous commands. Manual approval caught 14%.
275
103
30
3,924
552,232
Dan Gora retweeted
The Claude Security plugin for Claude Code is now available in beta. Scan your changes for vulnerabilities before you commit, or run a full scan across your codebase, all from your terminal on the Claude inference you already run.
604
1,555
419
17,320
2,618,314
Dan Gora retweeted
well thats fucking it - anthropic has officially replaced software engineers. claude is now a 24 hr autonomous coding agent. claude can now operate your entire computer and CLAUDE CODE = end-to-end software engineering: - claude writes the code for you - then literally opens the app it coded - clicks through the entire app and find bugs - then fixes the bugs and improves the app in hours. previously claude generated code, you run it and give claude feedback. thats completely gone now. all in a continuous loop without leaving your terminal 😂 we're barely through monday. well done lol
Computer use is now in Claude Code. Claude can open your apps, click through your UI, and test what it built, right from the CLI. Now in research preview on Pro and Max plans.
462
310
55
5,977
1,157,269
🚨 Breaking: The guy who created Claude Code @bcherny just revealed how his team actually builds software with AI. And it’s not prompting. It’s a 5-layer operating system for AI-driven development. Most developers only use: • one Claude session • long prompts • manual reviews • sequential work Boris’s team does the opposite. They run Claude like a parallel engineering org. Here’s what he shared: 1. Parallel sessions (not one AI) They run 5–10 Claude instances at once. Each handles a different task. One writes code One reviews One tests One refactors Everything happens in parallel. 2. Persistent memory via CLAUDE.md They keep a shared CLAUDE.md in the repo. It stores: • past mistakes • architecture rules • coding conventions • verification steps Claude reads it every session. So the AI improves over time. 3. Custom AI subagents Instead of one Claude, they define roles: • backend-reviewer • migration-guard • code-simplifier • verify-app Each agent has a specific job. Like a real team. 4. Worktree isolation (true parallelism) Each agent gets: • its own git worktree • its own task • its own tests • its own PR No context collisions. No waiting. Just parallel execution. 5. Orchestration commands They use compound commands: /simplify → runs multiple reviewers in parallel /batch → launches dozens of agents → each opens a PR This enables: • large migrations • repo-wide refactors • automated reviews • parallel implementation The insight: This isn’t one AI assistant. It’s an AI engineering system. Parallelism Memory Custom roles Isolation Orchestration Stack them together and Claude stops behaving like a chatbot — and starts behaving like a team of engineers. This is what most people missed. They copied prompts. Boris built infrastructure. Bookmark this. This changes how you use Claude Code.
14
17
77
5,036
A senior Google engineer just dropped a 421-page doc called Agentic Design Patterns. Every chapter is code-backed and covers the frontier of AI systems: → Prompt chaining, routing, memory → MCP & multi-agent coordination → Guardrails, reasoning, planning This isn’t a blog post. It’s a curriculum. And it’s free.
1,637
797
40
4,622
651,438
99% of people using Claude are doing it wrong. They’re prompting. Not building systems. Not automating GTM. Not printing leverage. Meanwhile, a small group is using Claude to run: • Full GTM workflows on autopilot • Sub-agents working 24/7 • MCP-powered systems that replace entire teams That’s the gap. So I spent 100+ hours building The Claude GTM Engineer’s Bible — everything you actually need: • 1300+ battle-tested prompts • Claude Code + WAT framework setup • MCP, agents, automations (step-by-step) • Real GTM systems you can deploy immediately Not theory. Execution. I’m giving it to only 500 people. Want it? Follow me Must (so I can dm) Rt + Like Comment “CLAUDE” I’ll DM it. Miss this → stay stuck prompting.
68
45
99
11,312
Dan Gora retweeted
Best GitHub repos for Claude code that will 10x your next project: 1. Superpowers github.com/obra/superpowers 2. Awesome Claude Code github.com/hesreallyhim/awes… 3. GSD (Get Shit Done) github.com/gsd-build/get-shi… 4. Claude Mem github.com/thedotmack/claude… 5. UI UX Pro Max github.com/nextlevelbuilder/… 6. n8n-MCP github.com/czlonkowski/n8n-m… 7. Obsidian Skills github.com/kepano/obsidian-s… 8. LightRAG github.com/hkuds/lightrag 9. Everything Claude Code github.com/affaan-m/everythi…
131
861
46
5,580
524,693
Dan Gora retweeted
Thank god MCP is dead Just as useless of an idea as LLMs.txt was It's all dumb abstractions that AI doesn't need because AI's are as smart as humans so they can just use what was already there which is APIs
The cofounder and CTO of Perplexity, @denisyarats just said internally at Perplexity they’re moving away from MCPs and instead using APIs and CLIs 👀
686
327
193
6,135
2,293,561
Dan Gora retweeted
Released today: /loop /loop is a powerful new way to schedule recurring tasks, for up to 3 days at a time eg. “/loop babysit all my PRs. Auto-fix build issues and when comments come in, use a worktree agent to fix them” eg. “/loop every morning use the Slack MCP to give me a summary of top posts I was tagged in” Let us know what you think!
557
826
325
12,717
2,144,924