Execution harness · your own Claude subscription
Run your chats on Claude Code
Pick Claude Code as the harness in any thread and the round runs on the Claude Code CLI under your Claude subscription — the mesh tools, nodes and context you already have, driven by a different engine.
What installing does
Installing places the harness in your chat picker only — it lands at {you}/Harness/ClaudeCode.
It never appears for users who haven't opted in, because it needs a personal Claude subscription:
there is no shared key and nothing is billed to the mesh.
- Get the plugin — the harness appears in your thread's harness picker.
- Pick it in a thread, then run
/loginand choose browser login. Open the authorization page in a new tab, approve access, and paste the complete authorization code back into Memex. Your login is saved and refreshed by Claude. - Chat as usual — same threads, same tools, same mesh content.
Uninstalling removes it from your picker again; threads that had selected it fall back to the standard MeshWeaver agent path, so nothing breaks and no history is lost.
Good to know
- The deployment must load
MeshWeaver.AI.ClaudeCode, this package's runtime module. Getting the package is your personal picker opt-in; theFeatures:Ai:Clis:ClaudeCodeflag alone does not install or load the module. - It is an option of the shared Threads app — there is no separate app tile; install it, see its marks and open its settings there. Provider-specific authentication begins after you select the harness and run
/login. - It is a harness, not an agent: it changes what executes the round, not which agent you talk to.
- Each thread is one Claude Code session: every round resumes it, so the CLI keeps the thread's context and tool results itself. How the harness drives the CLI: @@("HeadlessProtocol").
- Nothing is shared. Your subscription, your login, your picker.