I’m working on a project that makes switching between coding harnesses essentially unnoticeable. It’s particularly useful when I run out of credits on any given day

The entire platform is skill driven, and based on the premise that state is your local file system. That makes switching harnesses so easy

It’s all open source and has plenty of other features, including inter agent communication, telegram client and much more in the pipeline

https://www.woltspace.com/

Not sure what the problem with switching is? When I run out of my kimi session, I just switch model and tell deepseek to continue. Yes I eat the initial cache miss but that's it, no fancy harness required.

I think having a codebase that can use any harness is the optimal setup. I often switch between harnesses and models all the time at work. We have our state/spec stored in git, so we can pack it up on friday and start fresh on monday. Or more commonly, using gemini/opus to create rich specifications and using Luna to implement them. Then switching again for reviews etc.