
Building & optimizing AI agents @DecagonAI. Sharing real lessons from enterprise deployments and agent experiments. Prev PM, VC, SWE.
Joined December 2021
- Tweets409
- Following314
- Followers322
- Likes572
Pinned Tweet
Game design explains the shift in how agents should work better than most AI takes right now.
We’re moving past heavy steering.
The parallels are clearer than people realize.
another banger by colussus, but who's surprised
colossus.com/article/sane-as…
very powerful anecdote from 1998 on the growing power and meaning of online communities. i read more about humans' relationships with technology these days as ai gets more intertwined with our lives
a story about a tree
raphkoster.com/games/essays/…
if all personal agents can bring pricing power back to consumers like grokbot just did, instinct's 30B valuation may just be worth it
shoutout grokbot for helping me find @spaceship for buying domains
running it back
We're running this back next Tuesday, 11/3! cc @Somil_Agg
If you want a great poker game and even better conversation, shoot one of us a DM
unsurprisingly, replit argues that deferring to a model's native ability to spawn subagents with limited steering is optimal
logical for a non-lab to argue this point since labs are incentivized to select their own models for subtasks rather than the MOST cost effective model out there
vendors whose value adds include being model agnostic (replit, cognition) should aim to take advantage of this limitation
great piece by the replit team breaking that down here: replit.com/blog/free-the-mod…
over the past 2 days, I've been understand why ramp's technical blogs hit so well
selfishly want to apply these principles to my own writing
at their core, ramp's writings:
- feel like they were written for their internal teams
- are honest
- anchor their pieces around "what was understood" and 1) what they did differently, and 2) why
will be stealing this formula for my own writing, thanks Ramp
another installment of forward deployed chips poker night bringing together NYC ai future founders, cohosted with @Work_Bench and the great @ProbyShandilya
shoutout the awesome people from @DecagonAI,@OpenAI,@percepta,@SierraPlatform, and @DistSpectrum
some notes from our convo:
- personal agents are actually being used, the best one is still disputed
- software factories don't seem totally real just yet
- harnesses still matter
- distributed systems are underserved by ai agents
Somil retweeted
marketing team advised that I shitpost less and try to provide some real value to the world, so here's what I've been working on recently!
To anyone who says the harness doesn’t matter, I ask you to read how Cockroach Labs built their harness designed for quality over throughput
Harness decisions I thought were smart
1. A separate agent review of scope suggestions and plans
2. A pr review agent that makes sure all steps have been followed before pushing to human review
3. Revisiting instructions / context buildup periodically - only finding 23% redundancy seems really low from my experience but could point to building up context efficiently
a couple of reflections on the new code review process from the Claude code team at Anthropic:
- they are playing a different game, I counted 5-10+ separate agent runs per PR which eats up so much context only a lab could bankroll
- they've created incentives that promote ownership, the approver for a PR is responsible for any bugs or issues in production
- review agents require quite a bit of restrictions (max # of turns, classifying bug severity, etc.)
- standardizing the review process is still an open design problem
- PREDICTION: there's going to be a more efficient way to see a snapshot of your codebase than having Claude generate a fresh artifact or summary each time
- there's going to be (or maybe already is) an open source repo that provides a list of model-agnostic best practices that will be widely adopted
claude.dev/blog/solving-code…
Really good quick snapshot on why salesforce acquired braze
$CRM just agreed to acquire $BRZE for ~$5.7B in cash bringing in a real-time customer engagement platform that had been taking customers from Salesforce’s own Marketing Cloud.
The acquisition gives Agentforce ability to act on live customer behavior while adding Braze’s usage-based revenue model as AI agents increasingly challenge traditional per-seat software pricing.
now that agents do most (all) of coding, my apis should be mcps, and I needed a way to convert for my personal codebase
but I wanted control over the conversion and scalable permissions
So I built agentifyapi. I built it all with @bot and am blown away
it does a few things:
- every tool starts disabled
- nothing goes live until I approve it
- changes show up as diffs, with one-command rollback
- Emails, phone numbers and card numbers get redacted
Free and open source. check pip install agentifyapi
github.com/SomilAgg123/agent…
insanely good piece from @dexhorthy at @humanlayer_dev on why software factories (still) fail
things dex calls out as necessary:
- design docs
- system design visualizations
- call-stack trees and file-tree diffs
- vertical slices
in shipping with personal codebases, ive seen the need for the same level of review as part of the software factory
what's cool is i've seen you can embed these visualizations into each agent's run in your agent.md when the PR scope is big enough, so it's pretty trivial to implement this kind of visibility
github.com/humanlayer/advanc…













