Patrick Lu

The B+ employee pandemic is real. Always "on it." Calendar blocked. Slack green. Never misses a deadline. Company still not moving. Bc they're all professional seat warmers. No edge. No urgency. Never fixing any gaps. They won't push back on anything. Just smile, execute, cash checks. Founders love them because they're "low maintenance." But what they actually are is low impact. U can have an entire team of B+ employees and wake up a year later in the exact same spot. Congrats, you’ve officially normalized mediocrity.

@maxviolition @svpino A more in depth post if you’re interested: x.com/lightninglu10/…

Each is working on a different feature. Manage them by kicking them off and checking in periodically. Each of them after a certain point need no hand holding. UX of my app shows me when it needs my attention. Each agent goes thru gets reviewed by another agent in GitHub, gets the review back into its own context, then verifies its own work by spinning up its own servers and QAing like a human would. Works incredibly well. Linked is my commit chart. This isn’t vaporware, it’s real software being shipped to real customers. Hth

I don’t believe people who say they are running “12 parallel coding agents”. Either they are lying for clicks, or I’m a complete retard who can barely keep up with a single Claude instance.

@a16zwagie @DissidentClint Lmao. Why didn’t I just use my hands to fold them then? 😂

@lightninglu10 @DissidentClint use ur hands dude lol

This is incredible. $2500 to never fold laundry again! WUT Many people are creeped out by humanoid robots. The aesthetics of this are a game changer.

@rezoundous 23 agents running here 👋

Does anyone actually run 20 agents in parallel?

@darreljlewis1 @RameshNivedita If you’re low IQ, then you’re low IQ That’s the tweet

@lightninglu10 @RameshNivedita I read hoping it was going to be interesting. Turns out if you suck at managing change, you suck at AI. That’s it, that’s the whole article.

One of the sharpest views I’ve read on AI and it’s impact at work

If you’re still writing code / watching code be written, you’re 6 months behind If you’re still reviewing code, you’re getting lapped If you’re still running a dev server, you’re so out of the game that your competitor has run circles around you Happy building ✌️

@Jason I’m in

We started an AI founder twitter group... reply with "I'm in" if you're a founder and want to be added

@prateeks PDFs work great but web pages don’t? Brother do you know that AI sucks at reading pdf’s? A whole business Reducto exists cuz AI is terrible at deciphering pdf

Founders, when you share your decks with investors, please share formats that are easier for humans and AI to work with. It is a good assumption that the investor you are reaching out will have some AI processing step in their workflow. PDFs work great! The docsend, gamma and other web formats create friction for the consumer of your deck and do not add much in terms of experience.

@ahmad_roumieh DMs closed 😁

If you want an intro to the speedrun team, hit me up! (Dms open)

PSA: don't put secrets you actually care about in Vercel to begin with. Anything prefixed NEXT_PUBLIC_ is in every visitor's browser by design. Everything else is "private" only as long as your host is. And you really shouldn't be running serious backends on Next API anyways

@MatthewBerman We built this with codepress.dev/terminal Full worktree / workflow isolation so you can work with as many agents as you want (we often do 10 at a time)

How are people running multiple agents at the same time? I’ve tried separate worktrees but things still get messy. I want separate environments for every agent thread. How can I accomplish this locally?

Wot.

@brettcalhounn 😂

The best founders to invest in are the ones who don't want our investment.

@kenanhsaleh @a16z @speedrun Would love to chat!

I'm opening my calendar for 1:1 office hours today and next Friday Applications for the next @a16z @speedrun cohort open next week - come AMA before they do. Happy to chat about your idea, fundraising, or application strategy Reply and I'll DM a Calendly link for 15-min slots

@brycent MIA --> Party

SF → B2B NYC → Consumer MIA → 🤔

We 5x'd the quality of AI working in our codebase. Not by switching models, not by better prompts. By building auto documentation that runs every time we ship. Here's why this matters more than people realize. THE PROBLEM WITH GREP When an agent works on a codebase, the default workflow is grep. Need to understand how user sessions work? grep → 50 hits → read each → grep again → repeat. Three things break: 1. Grep returns matches, not understanding. The agent sees WHERE, not WHY. Can't tell canonical from legacy. 2. Every grep-and-read cycle burns context. Agents end up with 30 files loaded and still miss the architecture. 3. Some things aren't greppable. Why does this code use a custom retry loop instead of the library? That answer isn't in the code — it's in someone's head. WHAT WE BUILT Not "better docs." A knowledge graph. codepress_documentation/ ├── INDEX.md └── features/ ├── agent-sessions/ │ ├── README.md │ ├── redis-protocol.md │ └── session-lifecycle.md ├── authentication/ │ └── README.md └── ... One INDEX file is the root: every feature registered with a slug, area, and one-line summary. Each feature gets its own folder with a README: architecture, key files, keywords for discovery. Complex features have sub-files: Redis protocol, session lifecycle, OAuth flows, linked from the README. CLAUDE.md / AGENTS.md files at the right directory levels point agents to the relevant feature docs automatically. When an agent starts a task, it doesn't grep. It navigates the graph. INDEX → feature README → sub-file for details. Pulls exactly what it needs, nothing it doesn't. HOW IT STAYS FRESH Every merge to main triggers a CodePress automation. An agent reads the diff, decides if the change is worth documenting (skips refactors, lock files, typos), classifies new feature vs update, writes or amends the feature doc, updates the root INDEX, updates the relevant CLAUDE.md / AGENTS.md WHY IT WORKS — ACCURACY Docs are denormalized context. One file replaces 30 grep results. Docs explain WHY, not just WHAT. Docs surface historical context that isn't in the code. WHY IT WORKS — SPEED Agent grepping and reading 30 files = 2-3 minutes wall-clock. Navigating to one feature doc = ~10 seconds. Multiply that across every agent run, every day, every engineer. You're running a different pace entirely. THE BIGGER INSIGHT Every system in your company was designed for humans. File structures. Runbooks. Process docs. Dashboards. Codebase layouts. All optimized for how humans think, read, and navigate. That's the wrong abstraction now. The companies that win the next decade won't be the ones with the best models. They'll be the ones who rebuilt every system — code, docs, ops, knowledge — to be legible to agents. Start with docs. Move to runbooks. Then internal tools. Then the whole stack. The AI didn't get smarter. The codebase became legible to AI. Most "AI doesn't work in our codebase" stories are really "our codebase isn't legible to AI" stories. Built this inside CodePress. Happy to walk through how if you're thinking about this.