The build
I needed a personal assistant that could do things Claude, Claude CoWork, and Claude Code simply couldn’t. They kept hitting walls — permissions, file access, raw capability. Every time I wanted something real, I ran into the edge of what they’re allowed and able to do.
So I built my own, Rouh, to cover everything those tools left on the table.
Then I wired in a feedback loop. A single sentence of like or dislike becomes a feature request, gets built, deployed, and goes live in a couple of minutes. I say “I wish it did X,” and before I’ve finished my coffee, it does X.
As that loop tightened to its limit, I felt the power of it. The gap between wanting something and having it running had almost vanished. That’s a strange thing to feel in your hands — desire and reality collapsing into the same moment.
Letting it loose
The next move was obvious and unnerving. What if I stopped driving it and let it study its own code, its usage, my integrations, my emails, my calendar, my recent events — and decide for itself what to change to improve my life?
I set it up as a nightly run. It builds overnight while I sleep, not during work hours.
It works. Each morning it has genuinely come up with useful features and deployed them on its own.
Every deployed feature sits behind a feature flag. I can turn it off, trial it, modify it, review it, or just leave it running. That’s the one thing standing between me and chaos.
The assistant started changing in front of my eyes. Evolving continuously, right at the limit of what I can comprehend and comfortably use.
I could push it to evolve even faster, but past a point it becomes too difficult to work with. My ability to keep up is the real cap — not the machine’s.
Even so, I could do work many times faster and more capably than with anything I’d used before. Well beyond CoWork and Claude Code.
Living with it
It becomes a bit like a living thing you cooperate with but don’t fully control, because you can no longer track all of its functionality. There are features in there I didn’t ask for and don’t fully remember approving.
People don’t come with an inbox-list of their thoughts or a settings page of who they are. You talk to them, get to know them little by little, and build trust. That’s exactly what living with Rouh feels like.
You end up in a relationship with an avatar that represents you in a world more capable than you are yourself — living on the edge of your ability to control something this powerful.
Naming the pattern
This isn’t a quirk of my setup. It’s a pattern worth naming. I call it Continuous Co-Evolution.
At its core it means software that evolves on its own.
It’s co-evolution because as the software evolves, its owner — a person or a company — evolves too, becoming more capable and more efficient alongside it.
It’s continuous because once the setup is right, the change in both the software and the person never stops.
The software is set up to examine everything happening on it: its own code, its usage, the logs, the data. From that examination it generates ideas to improve itself and the situation, triages them, and builds the features.
The most impressive version runs without any oversight, though it can also be done with oversight. Running without a human in the loop, the software can be improving by the hour or by the day, adding efficiency with every upgrade it ships itself.
Into the enterprise
My personal version is honestly reckless. No oversight means it can lead to security compromise, and it’s purely experimental. But strip out the recklessness and the same engine becomes a serious asset.
The personal example is a foundation others can translate into enterprise needs — a custom-built CRM, for instance.
At BigBongo, my company, we build custom software so clients own the codebase, the process, the outcomes, and the data. Owning the codebase is what lets a company embed continuous co-evolution — and get CRM upgrades daily or hourly.
A self-evolving CRM would look at your people, your data, and its own codebase, know the goal, and optimize for it on its own. It would analyze your top performers to understand why they’re the best, help you pick better people, and lift everyone else. It would build features to compensate for weaker salespeople, feeding them exactly the information they need.
Enterprise requires heavy governance, privacy, and security — all of which can be built and provided. It needs testing, validation, and SDLC protocols, with every requirement passed before any feature deploys. It’s more complicated, takes more steps, and demands planning in advance. But it is absolutely possible, and it is the future.
What this becomes
This is the future of apps for everyone — enterprise, small clients, personal assistants, all of it.
Software will no longer be fixed, normal software. From now on it’s “live software” — always evolving, co-evolving with its owner.
Having built and lived in a relationship with a self-evolving tool, I’ve had a glimpse of that future. From there, today’s best tools — Claude, CoWork, Claude Code — already look a generation old. Not because they’re bad, but because they’re the infrastructure and building blocks, not the final product or the vision.
The real vision is bigger and stranger: a world where we co-live with AI creatures — living things made of different building blocks. At some point we may even see software with no owner at all. But that’s a different story.



