[2001zhaozhao]

There is a new breed of agent-agnostic tools that call the Claude Code CLI as if it's an API (I'm currently trying out vibe-kanban).

This could be used to adhere to Claude's TOS while still allowing the user to switch AI companies at a moment's notice.

Right now there's limited customizability in this approach, but I think it's not far-fetched to see FAR more integrated solutions in the future if the lock-in trend continues. For example: one MCP that you can configure into a coding agent like Claude Code that overrides its entire behavior (tools, skills, etc.) to a different unified open-source system. Think something similar to the existing IntelliJ IDEA's MCP that gives a separate file edit tool, etc. than the one the agent comes with.

Illustration of what i'm talking about:

- You install Claude Code with no configuration

- Then you install the meta-agent framework

- With one command the meta-agent MCP is installed in Claude Code, built-in tools are disabled via permissions override

- You access the meta-agent through a different UI (similar to vibe-kanban's web UI)

- Everything you do gets routed directly to Claude Code, using your Claude subscription legally. (Input-level features like commands get resolved by meta-agent UI before being sent to claude code)

- Claude Code must use the tools and skills directly from meta-agent MCP as instructed in the prompt, and because its own tools are permission denied (result: very good UI integration with the meta-agent UI)

- This would also work with any other CLI coding agent (Codex, Gemini CLI, Copilot CLI etc.) should they start getting ideas of locking users in

- If Claude Code rug-pulls subscription quotas, just switch to a competitor instantly

All it requires is a CLI coding agent with MCP support, and the TOS allowing automatic use of its UI (disallowing that would be massive hypocrisy as the AI companies themselves make computer use agents that allow automatic use of other apps' UI)

[chasd00]

Could you think of it as ClaudeCode is just a tool used by another agent and that other agent is instructed to use the ClaudeCode tool for everything? Makes sense, i don't see why we can't have agents use these agents for us, just like the AI companies are proposing to use their agents in place of everything else we currently use.

Also, why not distribute implementation documentation so claudecode can write OpenCode itself and use your oauth token. Now you have opencode for personal use, you didn't get it from anywhere your agent created it for you and only you.