conductor-remote 1.69.0 → 1.71.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
@@ -254,7 +254,7 @@ RELAY_TOKEN=$(openssl rand -hex 16) yarn start
254
254
  `conductor-remote mcp` is an MCP server on stdio. It gives a coding agent the same
255
255
  control the phone has, over the same relay.
256
256
 
257
- Two transports, same sixteen tools.
257
+ Two transports, same seventeen tools.
258
258
 
259
259
  | | |
260
260
  |---|---|
@@ -265,6 +265,7 @@ Two transports, same sixteen tools.
265
265
  | `split_chat` | move a tangent into a fresh tab, carrying the conversation across as a Conductor attachment |
266
266
  | `list_models` · `set_agent_options` | cached model labels, model, effort, plan, fast — Conductor keeps these in its UI and nowhere else |
267
267
  | `set_workspace_status` | move a workspace between the sidebar's status groups |
268
+ | `archive_workspace` | put a finished workspace away (Conductor's ⌘⇧A) — deletes the worktree, keeps the chat |
268
269
  | `dismiss_prompt` | throw away a prompt the relay is still holding |
269
270
  | `keep_awake` | hold this Mac awake with the lid shut, so a long run stays reachable |
270
271
  | `relay_logs` | the relay's own log — why a send failed |
@@ -272,7 +273,7 @@ Two transports, same sixteen tools.
272
273
  **Name it `conductor-remote`, not `conductor`.** Conductor injects an MCP server of its
273
274
  own into every agent it runs, and that one is already called `conductor`. Register this
274
275
  under the same name and inside a Conductor workspace the two collide: Conductor's tools
275
- win, these sixteen vanish, and the only trace left is this server's instructions text —
276
+ win, these seventeen vanish, and the only trace left is this server's instructions text —
276
277
  so it reads as if the tools should be there.
277
278
 
278
279
  **stdio** — for an agent running on this Mac. The client spawns it as a child process;
@@ -322,11 +323,12 @@ of the time.
322
323
  | `send_prompt` | send into an existing chat (drives the real UI) |
323
324
  | `stop_turn` | cancel a running answer (drives the real UI) |
324
325
  | `set_workspace_status` | set the sidebar status (drives the real UI) |
326
+ | `archive_workspace` | archive a workspace (drives the real UI, deletes the worktree) |
325
327
 
326
328
  The first six touch nothing. `create_workspace` opens a Conductor deep link, so
327
329
  creation needs no Accessibility and steals no focus. Requested model, effort, plan,
328
330
  and fast settings are applied later through Conductor's UI, before the relay sends
329
- the first prompt. The last three drive Conductor's real window for a few seconds.
331
+ the first prompt. The last four drive Conductor's real window for a few seconds.
330
332
 
331
333
  The HTTP transport is deliberately minimal: the server never initiates a message, so
332
334
  there is no SSE stream and `GET /mcp` answers 405, which the spec allows. It keeps no