Attending the YC event in Stockholm or Agentic Dev Days tomorrow? Just flying over, too!
Right after the event moving straight to SF with our startup, @prelint_ai , and flying from Stockholm.
Would love to grab a coffee if I can be of help. Also: we built an AI that surfaces product drift and implicit decisions your coding agents made on your behalf and I'm looking to run it by as many AI-pilled founders as possible.
@wojtekszkutnik@aiamblichus that's the setup imo. greptile + prelint is basically catching the footguns before they escape. the fact that you can still review architecture separately is the real W
The pattern with AI agents is always the same: give them more autonomy, velocity goes up, everyone gets excited, then something breaks.
The hard part isn’t the fix — it’s figuring out what actually happened. AI workflows no longer follow the “one engineer, one PR” model. You’ve got multi-agent runs, parallel terminals, cascading edits, and a web of invisible assumptions.
When failures hit as side effects — silent cost spikes or wiped logs — post-mortems become a real bottleneck. The AI skips checks and just assumes it’s right.
This is the real limit on AI coding now. It’s not about generating better code anymore. It’s about visibility.
That’s why we’re building @prelint_ai . We monitor in real time and preserve the thread of intent so you don’t lose context every session.
If you’ve ever let an LLM run for a day without a human in the loop, what surprised you most when you reviewed the work afterwards?
#AIAgents #DevTools
200 people showed up on a Sunday to build with AI and Prelint. Big thank you to all attendees of our NYC hackathon - impressive how much you shipped in a matter of a couple hours!
Are you in New York?
We’re excited to support the Pioneering Minds AI Grayscale Hackathon in NYC this Sunday! 🚀
Every participant gets free access to Prelint during the hackathon. We’ll be there to show how it keeps your coding agents aligned on real pull requests when things move fast - like in a hackathon.
@_CallMeMacy sounds like @prelint_ai - applied!
we sit on top of coding agents and catch product drift - the small deviations they introduce that compound over time.
ends up being responsible for ~35% of all code and docs improvements, with only ~4% overlap with technical code review.
prelint now handles pr approvals properly and keeps your pull requests clean without comment duplicates
clean diff → approve
same commit, no changes → skip
new findings on next push → dismiss the stale approval
At the beginning of the year, I was trying to solve a specific problem - AI coding agents making a mess and adding unnecessary tools and features. So we built prelint.
Two weeks post-launch, it's catching issues no other AI reviewer does and is responsible for 30% of agentic feedback we are acting on!
Prelint is catching up much faster than we've ever expected.
For some projects, we're seeing 30%+ of all revisions to be the result of prelint's comments!
@GithubProjects Prelint - an AI Agent that makes sure your code aligns with product intent, business rules, compliance constraints, and strategic decisions.
It provides feedback to your coding agents via PR comments on GitHub!
https://t.co/y4DBPshlQI
"Why do you even need product review for pull requests?"
With agents writing most of the code and the pace only accelerating, product drift compounds - an agent introduces a misplaced dependency or assumption, and before you know it, it's baked into your product for good.
With Prelint, every PR gets checked against your product specs before it ships - a feedback loop that helps coding agents course-correct without human intervention.