Thanks for your evaluation.

I've deliberately been post-poning harness building.

I think it's great as an obligatory learning experience.

But I'm hoping someone will come along and provide the "best of breed" harness:

  - OpenCode's TUI and client-server model,
  - Claude's prompt engine,
  - Pi's extensibility, and
  - the codebase stability of a craftsman (yet to be seen).

I haven't tried other harnesses than those three. It's time-consuming, and does not align with my primary goals.

I've been reimplementing a TUI library based on Ratatui, but drawing the UI components of OpenCode's OpenTUI and a bunch of Ratatui-adjacent components. Was hoping someone would separate the concerns and reverse engineer Claude's prompt engine and just not provide a UI for it. Make it modular so each part can be replaced by something better. There's only really 3 parts: TUI library, engine, and client-server (so you can choose between web or terminal, and so you can host the engine + server in the cloud, resume your sessions, and whatever enterprise features you want for session and memory management.