this is pure f*cking gold for anyone running coding agents
Jev founder Diogo Amogo wrote a PDF on building a Jev harness
the promise:
> 200x faster
> 400x cheaper
the model hasn't been the slow part for a while
the speed and the cost sit in the harness wrapped around it
• how to use it
> drop this PDF and the article below into Claude Code or Codex
> let it rebuild its own setup
one evening of setup
and your agent starts next week on a harness most teams still don't have 👇
This is an extremely good watch.
The things that felt novel/interesting to me:
1. Lock down your agents
Humans tend to like 'sharp knife' abstractions - that are powerful, but you can cut yourself if your use them wrong. Lauren says agents perform much better in extremely locked-down environments. Abstractions are designed so they can't screw up, and lint rules enforce it.
They built a whole internal framework (Dune) to keep the agent on track.
That helps optimise agents that don't have a large context window to work productively in your codebase.
2. Create verification infrastructure
To trust the results of any agent, you either need to sit and watch it OR have it provide evidence of its improvement. This has always made sense to me, but Lauren really pushes it hard here:
- Invest in custom CLI's that let the agent drive the app and measure its performance
- Make the app "factory ready" from the get-go - i.e. deployable to an environment where the agent can mess about with it
3. Feature Maps
Lauren's software factory (what she calls an 'outer loop') often requires the agent to break down vague bug reports from users and to turn those into potential fixes.
To aid that, they built a 'feature map' of all the main features in their application, which describe exactly how the app is supposed to function.
This has become essential for helping the agent navigate the codebase, and figure out quickly how things are supposed to work. It's maintained along with the codebase, and kept in sync via automations.
This is the kind of documentation I usually warn against. It goes stale quickly and can confuse agents if it's not kept up to date.
But Lauren's team are using it as critical navigation infrastructure, and it makes it possible for agents to explore faster and better - even on a large codebase. So it sounds like navigation docs like this are worth it if they enable new behavior.
Banger talk - watch the whole thing on 2x.
I need help - do you know of any food influencers?
need to pick their brain and potentially bring them on as equity partners
do your thing!
#buildinpublic