I was tired of "babysitting" my AI. So I spent 6 months building a C++20 Autonomous Software House that ships while I sleep

Reddit r/AI_Agents Products

Summary

Neon Sovereign is a native C++20/Vulkan autonomous software development workstation that uses a multi-agent swarm to execute software briefs end-to-end, running local LLM weights via Ollama/GGUF with no cloud dependency. The creator is seeking systems engineers and early testers as it enters Active Alpha.

Vibe-coders, I’m done with Electron-based sidebars. I’m done with "Apply" buttons. I’m done with chat assistants that lose context after 10 messages. We’ve been promised autonomous agents, but we’re still stuck in a cycle of prompt-and-wait. I wanted something different. I wanted a system where I define the Outcome and the IDE handles the Execution—natively, locally, and without supervision. Meet Neon Sovereign. It’s not a plugin. It’s not a wrapper. It’s a fully native C++20 / Vulkan workstation built to act as a deterministic software house. Why is this different? 🚀 Zero Latency: Built on a 120FPS Vulkan engine. No Electron bloat. It feels like silicon. 🤖 The Swarm: When you give it a brief, it doesn’t just "chat." An Architect generates a JSON Task DAG (Directed Acyclic Graph), and a parallel swarm of Specialist Developers starts building. 🧠 Amnesia-Free: It uses a persistent SQLite Memory Ledger (BM25) and a Context Vault. Your architectural decisions are never "lost" in the window. 🛡️ The Gauntlet: It doesn’t trust itself. It uses a ForgeMaster to verify cross-compilation in shadow buffers and a Silicon Retina (VLM) to actually "look" at the UI it builds in QEMU/ADB to check for layout collisions. 🔒 Total Sovereignty: Runs local weights (Ollama/GGUF). Air-gap friendly. Your context never leaves your box. The Workflow: Define the Brief: "Build me a cross-platform file sync tool with a GUI." Walk Away: Go grab a coffee. Handoff: Return to a forensic audit log, 37 passing unit tests, and a compiled .exe. I’m moving this into Active Alpha and looking for the systems engineers and vibe-coders who want to push the absolute ceiling of what agentic IDEs can do. If you’re sick of babysitting your AI and want to start orchestrating a swarm instead—check it out. PM if you would like to contact me.
Original Article

Similar Articles

I rebuilt my private "AI dev team" — which was secretly just a hardcoded workflow — as a substrate where orchestration emerges from instructions. Here's what I learned (and where it deadlocks).

Reddit r/AI_Agents

The author rebuilt their private AI dev team as an open-sourced substrate with addressable agents, reliable messaging, expertise discovery, memory, and isolated runtimes, allowing team behavior to emerge from natural-language instructions. They share insights on coordination challenges such as deadlocks and self-healing, and question how agent teams can collaborate using NL instructions.