Wink Pings

Agents Start Directing Agents; Troubleshooting Begins With Checking the Contacts

Conductor 0.95.0 opens up Agent permissions in local workspaces: it can create workspaces, ask other Agents to do work, wait for replies, and send follow-ups. After multiple Agents relay work, the spot most prone to problems shifts from writing code to handoffs.

Conductor 0.95.0 was updated on November 16, 2026. Agents in local workspaces can now start and manage other Agents. The official documentation is quite direct: have Claude Code, Codex, Cursor, or OpenCode create a workspace, start a conversation with another Agent, wait for its reply, and then send follow-up messages. Canceling and archiving conversations, archiving workspaces, setting workspace status, organizing workspaces into sidebar sections, and modifying a repository's setup/run/archive scripts are also within the permission scope.

The poster @yakami0129 raised a practical scenario: when you actually receive this kind of handoff, first check whether the previous leg clearly wrote down what was done and where it got stuck. Someone replied below that they first check whether it left input/output boundaries. Someone else joked that in the future you won't just need to see who is doing the work, but also who called whom to do the work; when troubleshooting, you'll first have to go through the contact list. Both comments point to the same thing: the quality of handoffs between Agents is more likely than an Agent's own intelligence to determine whether a task can be finished.

Here are a few other changes worth picking out. Conductor switched from Tauri to Electron; the official explanation is that it is faster and more stable, and makes it easier to locate problems. In chat, select text and click Add to chat or press ⌘L to quote it into the next message. There is no limit to how many conversations, terminals, or browser tabs you can open in a workspace. In repository settings, you can specify the run mode, set a certain action as the default, limit where it executes, and enable enterprise data privacy separately. After the sidebar is grouped by status, dragging a workspace to Backlog, In progress, In review, or Done changes its status.

Two fixes are worth noting. When archiving or restoring a workspace, there was a problem if shell code was embedded in the branch name; this is now fixed. Replying with the text USER_CANCELLED while asking a question would cancel the question; this is also fixed. The former is a security boundary, and the latter is a semantic collision; both are the kind that look small but become troublesome once you hit them.

There is another change that is easy to overlook: settings moved from the .conductor/settings.toml file into the app itself, and old configurations are imported automatically.

If you are currently running tasks with multiple Agents, think clearly about how to write handoffs before upgrading. Who started the work, what has been completed, where it got stuck, and who to hand it to next—these items do not have a fixed format, but if any one is missing, the next Agent has to guess. The cost of guessing wrong is higher than writing a couple more lines.

Source: Conductor 0.95.0 changelog

发布时间: 2026-11-17 13:25