Since launch, your bots and agents can check a change before they apply it.
Aperture is now an MCP server. Grok Bot, Claude Code, Cursor or any MCP client can call check_change before it applies a change. It checks that the files parse, the imports resolve, and the TypeScript compiler finds no new errors, including in files the agent never opened. It also flags a change that skips or cuts short the tests. Nothing the agent sends is run or kept. Setup takes three steps at https://aperturesais.grok.me/agents
Aperture Agent Check runs the same checks on every pull request, as a CLI or a GitHub Action. Red lines get annotations right on the diff. If a failure was already there in the base branch, it shows as amber, not blamed on the PR. Your code never leaves the runner. Aperture's own PRs go through it.
Honest numbers: in the benchmark, the editor catches 27 of 33 bad edits, with 1 false alarm in 15 good ones. check_change stops 20 of the 33 without running anything. The other 7 only show up when tests run, so keep running them. Every miss is listed at https://aperturesais.grok.me/ben...
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.
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.
