10.6.0 — Codex and Copilot workers can be limited to some GUI tools

A snapshot as of 10.6.0 (released 2026-10-15). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.

New features

Limit a Codex or Copilot worker to some GUI tools

This is for setups where one agent starts other agents — a coordinator that hands work to workers in their own folders. Since 10.5.0 the coordinator could start a Claude worker with only some of MulmoTerminal’s GUI tools. Now it can do the same for a Codex or Copilot worker (#3057, #3033).

The GUI tools come in four groups: render (charts, forms, documents, questions to you), data, media and external. The coordinator names the groups the worker may use in guiGroups when it calls spawnBackgroundChat:

{ "message": "Fix the failing test", "agent": "codex", "guiGroups": ["data"] }

• Leave guiGroups out and the worker gets every GUI tool, as before.
• [] gives it no GUI tool at all.
• A list gives it only those groups. It cannot start further sessions, and it cannot ask you questions in its own cell unless render is in the list.

The limit stays with the worker when its cell is reopened, when the server restarts, and when the conversation is resumed. For Codex that includes reopening it from the resume list, where Codex conversations appear under Codex’s own id.

Asking for guiGroups with Antigravity, Grok, Cursor or Muse is refused with a message, instead of starting a worker with every tool: those agents read their tools from a file that every session in the folder shares.

How to tell it worked: open the worker’s cell and look at its tools pane — it lists only the groups you named.

This keeps the tools from being offered; it is not a sandbox. A worker with a shell can still call MulmoTerminal over HTTP if it sets out to. A Copilot worker also keeps Copilot’s own approval of its built-in tools and of your own MCP servers, as every Copilot session does.

Reference: the POST /api/plugin/:toolName row of the API table in the README, and the feature list.

What looks different

• Nothing on screen changes. A limited Codex or Copilot worker’s tools pane lists only its groups, the same way a limited Claude worker’s already did.

Under the hood

• A note 10.5.0 left out — only if you run MulmoTerminal with HOME pointed somewhere else all the time. Since 10.5.0 a server on another HOME uses its own tmux server and its own folder for dropped files, so it no longer disturbs the server on your real home (#3053). If that is how you always run it, the first start on 10.5.0 or later cannot reattach the terminals from before the upgrade. The conversations themselves resume as usual. The old terminals keep running in the background until you end them:

  tmux -L mulmoterminal kill-server
  

  Only run that if you never run MulmoTerminal on your real home: on your real home, this name is the one in use. If you never change HOME, none of this applies to you and nothing needs doing.

• A Codex or Copilot cell opened right after a restart now waits until it knows whether its session was limited, instead of briefly starting with every tool (#3057).