Open-source AI code editor. Composer plans a change and stages it as a diff. Before you apply it, every change is checked: it parses, imports resolve, types check, the preview renders, and tests run. Tests run in your browser tab, free.
AI code editors are good at writing edits that look right. Whether the edit parses, whether its imports point anywhere, whether the tests still pass: you usually find that out after you've applied it. I built Aperture so the editor checks before you do.
Composer reads the code, posts a plan, and waits for you to click Build it. Edits arrive as staged diffs you keep or skip file by file. Nothing touches your files until you apply. Each staged change gets five checks: it parses, its imports resolve, the types check, the preview renders, and the project's tests run. A check that couldn't run says why. It never shows as a pass. If a test was already failing before the edit, Aperture says so and doesn't blame the edit.
The tests run in a sandboxed Worker in your browser tab with no network access, so they cost nothing and take about a second. It handles node:test, Vitest and Jest. A new failure goes back to the agent once to fix.
There's also a design mode: click an element in the preview to edit its CSS or the page's theme tokens. The demo plays recorded runs. To use a real model, self-host with your own key for Grok, OpenAI, Anthropic, Gemini, DeepSeek or a custom endpoint.
It's MIT-licensed. The demo asks you to sign in before you can run a plan. It plays back recorded runs, so it costs nothing. You can also run it locally in a minute without an API key; the commands are in the README.
What I'd like to hear: - Do the checks catch the mistakes that actually bite you? What's missing? - Where does the in-browser test runner fall over on your projects? - Anything that confused you in the first five minutes.
You used to wait on one Composer turn. Now hit the clock button (or Ctrl/Cmd+Shift+Enter), keep working, and open the run when it’s ready to review — up to three background runs at once. Checks still run on the result (parse, imports, real tsc, tests) before you keep anything.
Also new since launch:
Checks benchmark: how often the checks stop a bad edit before Apply — https://aperturesais.grok.me/ben... (18/18 visible mistakes stopped; 0/8 false alarms on correct edits)
Editable plans before Build, plus an agent board for every run
Real TypeScript type-check in the strip (not the light check)
Same product idea: plan first, exact lines, then checks — now it doesn’t block you while the agent works.
the "a check that couldn't run says why, never shows as a pass" line is the detail that'd actually make me trust this over other editors - that's exactly the kind of silent-pass failure I worry about with Claude Code when I'm not watching closely. one thing I'm curious about: the new failure goes back to the agent once to fix - what happens on the second miss? does it surface the diff to me with the failing test attached so I can see what it tried, or does it just drop the change and tell me it couldn't do it? that's the moment where I'd want maximum visibility, not a clean failure message
About Aperture on Product Hunt
“An AI code editor that checks its own work”
Aperture launched on Product Hunt on October 4th, 2026 and earned 64 upvotes and 10 comments, placing #33 on the daily leaderboard. Open-source AI code editor. Composer plans a change and stages it as a diff. Before you apply it, every change is checked: it parses, imports resolve, types check, the preview renders, and tests run. Tests run in your browser tab, free.
Aperture was featured in Open Source (68.9k followers), Artificial Intelligence (481.3k followers) and Vibe coding (711 followers) on Product Hunt. Together, these topics include over 148.2k products, making this a competitive space to launch in.
Who hunted Aperture?
Aperture was hunted by Witchayut Samnakhon. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Aperture stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Witchayut Samnakhon
Hi Product Hunt, I'm Witchayut.
AI code editors are good at writing edits that look right. Whether the edit parses, whether its imports point anywhere, whether the tests still pass: you usually find that out after you've applied it. I built Aperture so the editor checks before you do.
Composer reads the code, posts a plan, and waits for you to click Build it. Edits arrive as staged diffs you keep or skip file by file. Nothing touches your files until you apply. Each staged change gets five checks: it parses, its imports resolve, the types check, the preview renders, and the project's tests run. A check that couldn't run says why. It never shows as a pass. If a test was already failing before the edit, Aperture says so and doesn't blame the edit.
The tests run in a sandboxed Worker in your browser tab with no network access, so they cost nothing and take about a second. It handles node:test, Vitest and Jest. A new failure goes back to the agent once to fix.
There's also a design mode: click an element in the preview to edit its CSS or the page's theme tokens. The demo plays recorded runs. To use a real model, self-host with your own key for Grok, OpenAI, Anthropic, Gemini, DeepSeek or a custom endpoint.
It's MIT-licensed. The demo asks you to sign in before you can run a plan. It plays back recorded runs, so it costs nothing. You can also run it locally in a minute without an API key; the commands are in the README.
What I'd like to hear:
- Do the checks catch the mistakes that actually bite you? What's missing?
- Where does the in-browser test runner fall over on your projects?
- Anything that confused you in the first five minutes.
Thanks for taking a look.