Building Aperture in public — looking for builders who care about control before an AI edit lands
by•
Most AI editors edit first. Aperture shows the plan and the exact lines first, then checks the change before you keep it.
I’ve been shipping in public since launch (Background Composer is live). Not hiring full-time — looking for collaborators, advisors, and people building their own tools who want fewer wasted tokens and real control.
If that sounds like you: reply BUILD or DM.
61 views


p/runevr
p/producthunt
p/google-cloud-platform
p/aperture-7
p/raycast
p/kuc-kuc
p/lasso-11
p/kodlo
p/ai-context-flow
p/offiai
p/many-displays
p/reso
p/dino-kids
p/dex-by-exmergo
p/supabase
p/jev
p/htmldrag
p/murror
p/nexupira
p/jot-2-0
Replies
not BUILD, just a genuine question since I've been circling this exact topic in other threads this week. showing the plan and exact lines before the edit lands solves the "did I actually read this diff" problem, but does it also cover side effects that aren't visible in a diff - an API call, a db write, something that already happened by the time you're reviewing the plan? the part that's bitten people in my experience isn't the code change itself, it's the action a turn already took before you got a chance to say no
Good question, and a diff can't show you that. The plan and exact lines cover the edit. Scripts the agent runs, like tests and hooks, execute in a sandboxed worker in your browser tab with no network access, so code it just wrote can't hit an API or a db, and nothing touches your files until you click Apply. The gap is anything that runs outside that sandbox. That should be its own step you approve before it runs, and it's what I'm closing next. If you've seen a pattern that handles this well in those other threads, I'd like to hear it.