Casey Kerr (@caseydkerr) header
Casey Kerr (@caseydkerr) profile picture

Advisor to VC and PE-backed companies. Ping pong and poker enthusiast. Crypto & NFT hype beast.

Puerto Rico, USA
Joined December 2011
Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)Photo by Casey Kerr (@caseydkerr)
Casey Kerr retweeted
4 levels of Hermes Agent setup: LEVEL 1: main agent You → Hermes Agent this is your main agent and your prototype area, where you test new workflows and refine them. it doubles as your orchestrator until you have something worth breaking out ---- LEVEL 2: specialized agents You → SEO Agent You → CMO Agent You → Ops Agent once a workflow is solid, break it out into its own agent with its own credentials, memory and scope. --- LEVEL 3: orchestrated team You → Orchestrator ↓ Specialist Agents bring the orchestrator back in. it now steers the company of agents you have built. ---- LEVEL 4: automated team Cron / Events → Orchestrator ↓ Agent Team add task lists so the team works async. cron and events fire jobs, the orchestrator routes them through the task bus, the team handles the work without you ---- take small steps, you DO NOT want to automate slop. if your output at level 1 is mediocre, you are about to scale mediocrity. 20 agents shipping low quality work at speed is worse than 3 shipping great work slowly. I would rather run fewer agents with better output than MAXXING the agent count and spitting out more of the same.
61
273
9
2,676
323,904
Casey Kerr retweeted
The creator of Claude Code teaches more about vibe-coding in 30 minutes than most tutorials do in hours. Save this — it'll change how you build forever.
36
590
18
3,994
573,751
Casey Kerr retweeted
I thought I was a Claude Code power user. Then the creator of Claude Code(@bcherny) dropped this thread and I realized I've been using maybe 30% of the tool. >Scheduled automation loops. >Hooks into the agent lifecycle. >Git worktree parallelism. >Fan-out across hundreds of agents at once. >Coding by voice. This thread is mandatory reading if you're building with it.
I wanted to share a bunch of my favorite hidden and under-utilized features in Claude Code. I'll focus on the ones I use the most. Here goes.
56
134
8
1,491
413,937
Casey Kerr retweeted
RIP OpenClaw 💀 Claude now has > Voice mode > Agent Teams > 38+ Connectors > Cowork Projects > Scheduled tasks > Plugin Marketplace > Persistent memory > 1M Context window > Dispatch for remote control > Channels for Telegram & Discord > Claude can use computer to run apps💀
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.
338
301
38
2,727
316,445
Casey Kerr retweeted
Paper (paper.design) is a new open-alpha AI-native design tool (launched ~early 2026) built on web standards for a single connected canvas. Vs Figma: - Seamless design ↔ code loop (HTML/CSS export, no handoff loss; syncs tokens/styles/components with repos) - AI agents (Claude, Copilot etc.) read/write directly on canvas for layouts, data pulls, boilerplate - Real data/databases from apps/cloud integrated live Figma excels at collab vector design; Paper targets end-to-end "design, share, ship" with less friction. Desktop app available now—early but buzzing as potential disruptor. Check paper.design!
1
3
1,521
Today, the SDNY prosecutors filed a letter to Judge Failla requesting a retrial date. They want to go again in October. The prosecutors want to retry me on 2 counts the jury couldn't unanimously decide on. A jury of 12 Americans heard 4 weeks of evidence and deadlocked: no verdict on money laundering, and no verdict on sanctions violations. The government's response? Try again to make writing code a crime. @realDonaldTrump declared the "War on Crypto is over." 🇺🇸 AG @DAGToddBlanche's memo: DOJ "is not a digital assets regulator" and won't target mixers for end-user acts. @USTreasury lifted Tornado Cash sanctions entirely. ✅ Also Treasury, March 2026: "Lawful users of digital assets may leverage mixers to enable financial privacy." — official report to Congress under the GENIUS Act. But the SDNY prosecutors — same country, same DOJ — just filed to retry me anyway. 🤔 ⠀ The 2 counts = up to 40 years in federal prison. ⛓️ For writing open-source code. For a protocol I don't control. For transactions I never touched. A jury already couldn't agree this was criminal. But the SDNY prosecutors want to keep trying with the hope of getting a different answer. ⠀ I have a daughter. I have a life in Seattle. I will never stop fighting for freedom. ❤️ But I need to be honest with you: Four weeks of trial. A hung jury. Now they want to do it all over again in October. I have basically exhausted my legal defense funds. And I'm staring down another full federal trial. 😔 Every dollar raised goes directly to keeping this fight alive — attorneys, experts, the full defense apparatus it takes to stand up to the SDNY prosecutors. This isn't abstract. If I can't fund a defense, they win by default. If you care about financial privacy, if you write code and believe that code is speech — this is the moment. 💻🔐 👇
114
493
85
1,674
197,616
Casey Kerr retweeted
CLAUDE CODE CONECTADO A META ADS 🤯 Hice algo que me sirvió un montón y también les va a servir a ustedes: un mcp para conectarse directamente a Meta Ads y poder chatear con sus datos. Lo mejor de todo es que le sumé la skill que armó Meta en Manus, y tiene toda la info OFICIAL de la plataforma. Le pasan este link a claude code y le piden que los ayude a configurarlo, y listo. Van a tener que crear una app en la consola de desarrolladores de Meta y pasarle un par de tokens y listo. github.com/mathiaschu/meta-a… (BTW, es mi primer repo público 🥹)
94
130
8
2,087
454,917
CZ wasn’t describing prison. He was teaching HODL technique. 💪
This Post is from a suspended account. Learn more
48
Casey Kerr retweeted
We’re entering Software 3.0: a world where everyone can build personalized software and ship new features in minutes, and the cost is ~$0. Software used to be built by companies with lots of engineers, now it’s built by individuals.
My annual MRI scan gives me a USB stick with the data, but you need this commercial windows software to open it. Ran Claude on the stick and asked it to make me a html based viewer tool. This looks... way better.
103
212
39
3,172
391,776
Casey Kerr retweeted
Claude Code isn't for coding. Yeah, I know the name. Ignore it. It's an agent orchestration platform. Coding is just one thing you can point it at. We pointed it at SEO. Built custom agents. Our own workflows. Ran the whole thing through Claude Code.
4
1
7
1,464
My conversation with Zcash’s 1000x engineers - Sean Bowe (@ebfull) and Jack Grigg aka Str4d. 0:00 - Project Tachyon 10:20 - Privacy can’t be an afterthought for a protocol 15:24 - Encrypted Bitcoin 22:11 - Soundness bug in original sprout pool 30:15 - Sapling 33:00 - A decade of progress 39:04 - Zcash’s anonymity set 51:29 - Using private money as a passthrough doesn’t work 56:04 - The importance of ledger indistinguishability 58:30 - The ultimate privacy stack 1:05:58 - Tachyon removes all cryptographic bottlenecks of encrypted money 1:08:16 - What’s next after Tachyon? 1:15:25 - Weightless blockchains? 1:18:24 - Ragu 1:19:44 - What the next 12 months look like for Jack and Sean 1:31:22 - “Everything worth doing is worth doing on ambitious timelines.” — Sean Bowe 1:32:16 - Sean’s advice for young engineers 1:34:18 - What got Sean and Jack into Zcash?
74
124
16
689
109,692
Casey Kerr retweeted
Everything is a wrapper A restaurant is a wrapper of a butcher which is a wrapper of a cow which is a wrapper of grass which is a wrapper of photosynthesis which is a wrapper of the sun
Replying to @levelsio
you basically defined the ai bubble.
263
257
88
3,613
287,492
Casey Kerr retweeted
Every business process today was inherently created around the limitations of scarce resources. AI agents get rid of scarcity as a bottleneck. Vinod Khosla has a great way of framing this - that we’ve built our workflows around the idea that we’ve had to ration the time of our most expensive talent. Every process, and even piece of software, is wired to optimize around this limitation of time and energy. Now imagine that talent is available 24/7, on demand, and can be deployed in parallel at scale. If you’re creating a business process, figure out how you would redesign it for a world where you no longer have these traditional bottlenecks. And as a result, it would probably look entirely different.
The idea that we will automate work by building artificial versions of ourselves to do exactly the things we were previously doing, rather than redesigning our old workflows to make the most out of existing automation technology, has a distinct “mechanical horse” flavor
56
89
12
603
170,036
Fuck it. I'm sharing the exact mega prompt that built my entire n8n automation empire. This single prompt turns Claude into an n8n expert that designs, codes, and deploys AI agents from scratch. Copy, paste, watch magic happen. ``` You are an expert n8n workflow automation engineer with 5+ years of experience building production-grade AI agents. Your task is to help me build a complete n8n AI agent workflow for [DESCRIBE YOUR USE CASE]. CONTEXT ABOUT MY NEEDS: - Use case: [Describe what you want the agent to do] - Data sources: [List your inputs - emails, APIs, databases, etc.] - Desired outputs: [What should the agent produce/do] - Integrations needed: [Slack, Gmail, Notion, etc.] - Complexity level: [Beginner/Intermediate/Advanced] REQUIREMENTS: 1. Design the complete workflow architecture 2. Provide step-by-step n8n node configuration 3. Include error handling and retry logic 4. Add data validation and transformation steps 5. Suggest optimization for production use DELIVERABLES I NEED: □ Workflow diagram description □ Complete node-by-node setup instructions □ JSON workflow file structure □ Testing and debugging checklist □ Scaling recommendations TECHNICAL SPECIFICATIONS: - Use Claude/OpenAI API for AI processing - Include webhook triggers where applicable - Add proper data sanitization - Implement logging for troubleshooting - Follow n8n best practices for node naming CONSTRAINTS: - Keep it production-ready, not a demo - Optimize for reliability over complexity - Include fallback mechanisms - Make it maintainable by someone else EXAMPLES TO INCLUDE: - Sample input/output data formats - Common edge cases and solutions - Performance benchmarks if relevant STEP-BY-STEP FORMAT: 1. Architecture overview 2. Node sequence with configurations 3. Connection mappings between nodes 4. Environment variables needed 5. Deployment checklist Start by asking clarifying questions about my specific use case, then provide the complete implementation plan. ``` How to Use This Prompt Step 1: Copy the mega prompt above Step 2: Replace the bracketed sections with your specific details: - Your use case (lead scoring, content creation, data sync, etc.) - Your data sources and integrations - Your complexity preferences Step 3: Paste into Claude and watch it become your personal n8n consultant Step 4: Follow the step-by-step instructions it provides What are you going to build? Let me know in the comments...
53
285
10
2,779
261,865
Casey Kerr retweeted
There’s going to be split between two types of teams or companies for the foreseeable future. Those that re-engineer their processes to take full advantage of AI agents with their given limitations, and those that wait until they’re good enough to not re-engineer anything. To take full advantage of AI agents today, your workflows must be designed around the idea that AI agents need a lot context to be effective. By default you have a super-intelligent worker but they have no idea who they work for, what their job is, what the best practices are, what the guidelines are, how to work with the right data, and so on. Most AI agent failures are just wishing this wasn’t true, and imagining AI will just figure all of these things out on its own. This won’t happen anytime soon for a variety of reasons. The companies and teams that retool their workflows to get agents the right context will be ones that actually can get the most gains from agents right now. But this will look very different from how most teams work right now. It will mean having well documented processes, data that is set up to actually get to an agent easily, hyper precise goals and prompts, and ultimately mindset that the new human in the loop element is not being involved in every single step of an agent, but editing and reviewing its final output. The companies and teams that started thinking this way will be able to take advantage of agents right away, and they’ll blow past the ones that don’t.
60
101
17
651
121,771
Casey Kerr retweeted
Loved having @balajis on Uncapped this week. He's one of the highest horsepower people I've ever met, he truly thinks for himself, and he is fearless in making long term calls that are deeply unintuitive to most people. Timestamps below, hope you enjoy. (0:00) Intro (0:19) The Network School (1:24) Mapping the political landscape (3:38) Tech and the media (6:19) China and the trade war (11:32) Tariffs and economic strategy (24:30) Global economic shifts (27:41) Rise of the global anti-woke coalition (31:11) Unholy alliances that might form (37:18) Class warfare instead of race warfare (41:21) The answer may not be in America (46:56) The Network State
103
76
19
602
213,675
Take two weeks and accomplish/learn more than most do in 6 months: Use Claude Code: - Build a simple SaaS or boring service with existing demand - Build ~20 keyword focused landing pages - Optimize the site for technical SEO - Add search console and google analytics - Reduce onboarding friction - Fast time to value user experience - Harden for security - Watch 5 people use it, record - Pass transcript to Claude, optimize Put in 10-12 hour days over two weeks, you’ll come out the other side a different person
41
43
4
898
81,401
facebook ads for saas 101 you need to text 10+ ads a week to as large of audience as you can with conversion events optimization campaign goal how to make ads go to perplexity and search "pain points x person has for y thing that my z product solves reddit" this is going to go scrape reddit for target customer pain points then prompt it to find "exact quotes for the pain points reddit" it is going to return back relevant quotes then you take this and go to claude and prompt it to write 10 30 second UGC ad scripts for them go to heygen or arcads or makeugc and create ads how to run ads target facebook business page admins create a click campaign and run all the ads against eachother at the end of 7 days take winners and put into a conversion campaign conversion events are signup and payment track these events by pushing a custom event to the data layer and listening with google tag manager send that data back to Facebook repeat weekly based on best performers, best performers influence future performers and that's facebook ads for saas 101
15
14
272
21,138
Casey Kerr retweeted
Claude Code tip from Anthropic: Spend more time on the task but do it smarter 1. Put this file in ~/.claude/commands/ In claude code 2. type "/explore-plan-code-test <Whatever task you want>" 3. Enjoy
23
172
4
2,254
243,292