How does microManager run OpenCode?
The built-in OpenCode profile runs:
opencode acpin the workspace’s worktree and talks to it over the Agent Client Protocol. It uses the opencode on your login shell’s PATH, or the absolute path you set in Settings → Agents.
What works with OpenCode?
Streamed replies, tool calls as cards with file edits shown as diffs, its plan as a to-do list, permission requests, model choice and slash commands, plus microManager’s MCP tools. Worktrees, checkpoints, diff review and pull requests work exactly as they do for every other agent.
What happens to OpenCode chats when I import from Conductor?
ACP chats that Conductor ran with a non-Grok model become OpenCode chats in microManager, with the model name carried over. Their earlier messages are not shown, and a chat whose session Conductor kept in its own store, which no ACP agent can load, starts a new OpenCode session.
What do I need?
OpenCode installed and configured with at least one provider, so that opencode works in your terminal.