There are going to be a lot of tools coming soon that are "agent-agnostic", i.e. can run on CLIs including Claude Code. I am personally experimenting with using a combo of MCP + custom UI layer to provide custom tools with bespoke UX and thus turn Claude Code (or any other CLI agent for that matter) into whatever I want. I wonder how they'll deal with that.
For a good existing example developed by a known company, check Cline Kanban: https://cline.bot/kanban
They don't have the MCP-bundling idea that I'm experimenting with, however.
Some editor integrations are a bit like this already, where during use you don't actually touch the built-in TUI even for prompting or viewing the output and approving permissions requests.
I imagine how they treat these things will be contextual and maybe inconsistent. There aren't really hard lines between what they probably want editors that integrate with them to do and generic tools that try to sit a layer above the vendors' agent TUIs.