But I do use claude code tui because I have a sub: it is a good model and I like its aesthetics. If I could use the sub in my own harness I would. It's also a foil to GPT's models that overengineer everything.
I have a Codex subscription that I use in my own harness, dreamcoder.ai, which has a tiling window manager and all the other mod cons you'd expect a frontier harness to have.
In addition to that, I run Qwen 3.8 27B NVFP4 with ninfer on my 5090. It's a great model for local development. I also use that in dreamcoder.
I recently moved away from using tui to directly interact with claude code.
I still start a session in the terminal but then ask to start a simple jira- like ticketing system.
When I have a request I start a new ticket and claude decides to either do it or launch a sub agent to do it.
When claude is done or has questions- he replies in the ticket. When claude has a side-findings he creates a new ticket for me.
I also do orchestrator like work that way. The key difference is I'll have a master chat and let it delegate work as needed to sub agents.
I have skills, MCP etc for things that need it, and custom-designed sub agents for a couple of very specific, niche tasks. The rest use generic delegator, explorer, worker sub agents that just take normal instructions.
But I meant more like, you know: hey just use the whole sub in another harness. That you can't do.