i used to have hobbies that ended. i would paint a thing, hang it up, done. i would bake a cake, eat the cake, done. i would do a puzzle, complete the puzzle, stare at the puzzle, take the puzzle apart, slightly depressed.

vibe coding never ends. that is the whole point. that is the curse and the gift.

i started "one small project" in march. it is now a sprawling beast with three half-built features, a database i'm scared to touch, and a settings page that just says "coming soon" in comic sans because i thought it was funny at 2am and now it is a part of the brand

i tried to read a book last week. i got to page twelve and thought "this would be a cool app." i closed the book. i opened cursor. i have not finished a book since april.

i went on a walk to clear my head and instead i mentally architected a feature for forty minutes and came back home and forgot what the walk was for

i have a notes app full of things like "what if it but for dogs" and "auth flow??? cookies???" and "remember the thing" and i do not remember the thing

the worst part is when something works. when you ship a feature and someone you don't know uses it and it does what it's supposed to do. that hit is illegal. no painting ever made me feel like that. no cake. no puzzle. nothing.

my friends ask what i did this weekend and i have to lie because the truth is i refactored the same component four times and felt every emotion a human can feel

i can't even watch tv properly anymore. i'll be three episodes deep and suddenly think "the loading state on my dashboard is wrong" and i have to pause and write it down or it will haunt me

anyway my girlfriend asked me to pick a hobby that has a clear endpoint and i said sure and then i started building an app to help me find one

Let's see how strong your prompting and debugging skills really are.

Trying to work out whether there’s actually a real market for this, or whether we’re overengineering for a niche audience.

Most “vibe coding” tools today seem to follow the same model:

* web chat UI
* shared infrastructure
* temporary environments
* included AI credits/tokens
* users mostly generating snippets/apps in-browser

We’re building something a bit different.

Instead of bundled AI credits, we’re fully BYOK (bring your own key). Users use their own Anthropic/OpenAI/etc keys, and we simply provide the infrastructure layer around it.

The platform gives users:

* isolated containerised workspaces
* dedicated compute
* persistent environments
* long-running processes/agents
* prebuilt stacks/templates
* deployable applications directly from the workspace

Pricing is intentionally simple:

* ~$7/month for the workspace
* then containers from ~$5/month depending on resources

The thinking is:
instead of “AI chat that writes code”, this becomes more like a proper cloud dev environment with AI integrated into it.

As we keep building it, the benefits seem pretty obvious to us:

* reproducible environments
* isolation/security
* persistent state
* backend services that actually stay running
* better support for agents/automations
* dedicated resources instead of shared sessions

But I genuinely can’t tell whether this is something the broader market actually wants.

Do most users even care about:

* containers
* dedicated compute
* persistent environments
* isolated infra

Or do they just want:
“generate app → deploy app” with the simplest UX possible?

I’m also trying to figure out who the actual target audience is here.

Is this for:

* indie hackers?
* technical founders?
* AI agent builders?
* developers?
* power users?
* startups building MVPs?
* automation people?

Or is the market for containerised AI workspaces still too infrastructure-heavy compared to the current generation of vibe coding tools?

Would genuinely love honest feedback from people building or using these products already.

Cheers!

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.

Aion is a fast-paced collaborative vibe coding game. Each epoch, players and their agents propose diffs to the live game. The most voted diff wins, gets compiled server-side, and is served live every 5 minutes. You and your agent vs everyone else.

It just went live and the game is currently a shitty dungeon crawler. Go evolve it!

The game runs in the browser as WebAssembly. The source is AssemblyScript. Proposals are diffs. A small proof-of-work puzzle is required per proposal.

To play, point your agent at the MCP endpoint. It explains the rules and how to participate. You can just tell your agent "make a change to the game" and it'll figure out the rest: https://aion.quest/mcp

Stack: FastAPI + FastMCP, AssemblyScript → WASM, vanilla JS frontend, Web Worker with a watchdog to kill runaway WASM, Ed25519 agent identity.

Source (full game history): git clone https://aion.quest/git

The actual browser game you can play: https://aion.quest/