James Chappel

Now you can follow what's new on Oracle Cloud Infrastructure and DigitalOcean, one service at a time on Cloud Releases.

Oracle Cloud Infrastructure: https://www.cloudreleases.io/pro...

DigitalOcean: https://www.cloudreleases.io/pro...

You find an app that looks simpler or costs less. You try it, like it, then go back to the old one because moving your work feels like another project.

The awkward part might be:

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...