conductor-remote 1.42.3 → 1.44.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -228,20 +228,42 @@ RELAY_TOKEN=$(openssl rand -hex 16) yarn start
228
228
  `conductor-remote mcp` is an MCP server on stdio. It gives a coding agent the same
229
229
  control the phone has, over the same relay.
230
230
 
231
- Two transports, same ten tools.
231
+ Two transports, same sixteen tools.
232
+
233
+ | | |
234
+ |---|---|
235
+ | `search_chats` · `read_chat` | full-text search every chat on this Mac, archived included, then read one |
236
+ | `list_workspaces` · `list_chats` · `workspace_diff` · `list_repos` | what is running, and what it changed |
237
+ | `create_workspace` | start work in a repo, with an optional first prompt. Touches no UI |
238
+ | `send_prompt` · `stop_turn` | talk to a running agent, or cancel its turn |
239
+ | `split_chat` | move a tangent into a fresh tab, carrying the conversation across as a Conductor attachment |
240
+ | `list_models` · `set_agent_options` | model, effort, plan, fast — Conductor keeps these in its UI and nowhere else |
241
+ | `set_workspace_status` | move a workspace between the sidebar's status groups |
242
+ | `dismiss_prompt` | throw away a prompt the relay is still holding |
243
+ | `keep_awake` | hold this Mac awake with the lid shut, so a long run stays reachable |
244
+ | `relay_logs` | the relay's own log — why a send failed |
245
+
246
+ **Name it `conductor-remote`, not `conductor`.** Conductor injects an MCP server of its
247
+ own into every agent it runs, and that one is already called `conductor`. Register this
248
+ under the same name and inside a Conductor workspace the two collide: Conductor's tools
249
+ win, these sixteen vanish, and the only trace left is this server's instructions text —
250
+ so it reads as if the tools should be there.
232
251
 
233
252
  **stdio** — for an agent running on this Mac. The client spawns it as a child process;
234
253
  there is no URL and nothing is exposed.
235
254
 
236
255
  ```bash
237
- claude mcp add conductor -- conductor-remote mcp
256
+ claude mcp add --scope user conductor-remote -- conductor-remote mcp
238
257
  ```
239
258
 
259
+ `--scope user` because a Conductor workspace is a fresh worktree each time, and a
260
+ project-scoped server registered against your main checkout does not reach it.
261
+
240
262
  **HTTP** — for an agent that can only reach a URL, at `POST /mcp` on the relay, gated by
241
263
  the same token as `/api/*`.
242
264
 
243
265
  ```bash
244
- claude mcp add --transport http conductor https://<your-magicdns>/mcp \
266
+ claude mcp add --transport http conductor-remote https://<your-magicdns>/mcp \
245
267
  --header "Authorization: Bearer $(cat ~/Library/Application\ Support/conductor-remote/token)"
246
268
  ```
247
269