I wanted to automate simple vibecoding tasks, it evolved into pursuing an endless Claude Ultracode clone development.

Hey everyone,

A few weeks ago I got into vibe coding after discovering DeepSeek V4 Flash. The combination of low cost and surprisingly good results got me hooked pretty quickly.

After a few test projects, I had an idea: build a Python tool that could open ChatGPT, Claude, DeepSeek, and Gemini in separate browser sessions and have them work together like a council. Each model would know the original task, propose a solution, review feedback from the others, critique it, improve it, and repeat for a couple of cycles until they reached a consensus. The final result would then be passed to an "implementer."

This automated what i usually do as a vibe coder, which is check what chatgpt or claude has to say about some idea, plan or implementation.

It was a pretty simple Playwright + Chromium integration and I vibe-coded the first version in a few hours.

The results were actually great. Code quality improved, edge cases were caught more often, and integrations with existing features were generally cleaner. The downside was speed — every model had to wait for the others before proceeding.

That led me down the rabbit hole.

I started building a faster API-based only system and somehow ended up creating a fairly autonomous code-patching platform. It runs multiple batches per cycle, understands project context, project documentation, guardrails, Git history, and development guidance. I let it run autonomously for over 10 hours and reviewed everything afterward. Surprisingly, all of the proposed changes were legitimate findings.

Most of my effort has gone into making that one feature reliable.

The infrastructure for multiple agents is already there. Now it's mostly about preventing conflicts, duplicates between agents and making sure they consistently maintain the project's documentation.

Then I started building a "Creator Mode" that scaffolds entirely new projects. Right now it works reasonably well for Python, Node.js, and JavaScript projects, but every new language requires a lot of additional testing and wiring. I'd call this feature about half-finished.

The long-term idea is to combine Creator Mode and Patch Mode, add a few more specialized modes, and end up with a fully autonomous multi-agent development system that can self improve reliably. Something that can create projects, understand what it created, write its own documentation, generate future development plans, recover from failures, and provide a browser-based UX showing progress, architecture decisions, reasoning, integrations, and so on where the vibecoder decides how advanced they want different parts of their app developed, and accepts/denies new proposals.

The funny thing is that I've only spent about two weeks on this project, yet it already feels like a bottomless pit 😄

The hard part isn't coming up with ideas anymore. It's testing everything and making sure new features don't break existing ones.

At this point the project has around 4,250 tests. They're segmented so only 200–500 run for most tasks, but every new feature still adds another 30–100 tests. The test suite just keeps growing.

I'm honestly not sure whether I should keep going.

The ambitious (and maybe slightly delusional) part of me wants to push through and see how far this can go. The rational part of me thinks I've accidentally started building something much larger than I can realistically maintain alone.

Has anyone else fallen into a similar rabbit hole? Would you keep going, or call it a successful experiment and move on?