Airuncode

Several agents in parallel on the same repo is the part I'd want to hear more about. The failure I keep hitting isn't bad code, it's a second correct implementation of something the repo already had, because each session starts from a blank slate and it reads fine in the diff. Does the debate happen after all of them have read what's already there, or are they arguing about approaches before anyone checked whether one exists? Self-healing on a failed test worries me for the same reason, green doesn't tell you the fix belonged in that layer.

Hey Product Hunt 👋

I'm the builder of Airuncode.

I started working on it because I didn't want my entire coding workflow to depend on one AI company, one subscription, or one model.

The idea became pretty simple: the runtime should be the stable layer, and the model should be replaceable.

Airuncode runs locally on your machine, lets you bring your own API keys, use cloud or local models, run multiple agents in parallel, work directly on your files, execute tests and automatically attempt to fix failures.

I also built V-CORE into it, a native Vulkan 3D runtime, because I wanted agents to have real engine capabilities available instead of having to recreate rendering, terrain, physics and related systems from scratch every time.

Airuncode is already available to try on Windows, macOS and Linux.

This is still the beginning of the project. I'm actively rebuilding parts of the PWA, improving the experience and adding a community/forum where updates, bugs and feature discussions can live in one place.

If you try it, I'd really like to know two things:

What feels broken or confusing?

And what would make you actually use Airuncode as your daily coding agent?

Thanks for checking it out.