Execution harness · your own Cursor account
Run your chats on Cursor
Pick Cursor as the harness in any thread and the round runs on `cursor-agent` (Cursor CLI) over the Agent Client Protocol — the mesh tools, nodes and context you already have, driven by a different engine.
What installing does
Getting the plugin gives you access to it, and your harness picker offers the harness from the package — nothing is copied into your home (installations that still copy apps place it at {you}/Harness/Cursor).
It never appears for users who haven't opted in: 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 paste a Cursor API key (the browser login ofagent loginworks on the machine that runs MeshWeaver). - Chat as usual — same threads, same tools, same mesh content.
Uninstalling removes only a legacy home copy; it does not revoke your access, so the picker keeps offering the harness. Switch a thread to another harness to stop using it — no history is lost.
Good to know
- It is a harness, not an agent: it changes what executes the round, not which agent you talk to.
- Each thread is one Cursor session: every round resumes it, so the agent keeps the thread's context and tool results itself. Every tool the agent runs shows up in the thread as a tool call.
- The agent speaks the Agent Client Protocol; the harness that drives it is shared by every ACP agent and ships with the ACP Agents package: @@("Acp/AgentClientProtocol").
- Nothing is shared. Your account, your login, your picker.