mulmoterminal 4.22.0 → 4.23.0

package/README.md

@@ -1446,9 +1446,13 @@ question: can this CLI be handed a session-scoped payload on a per-spawn flag? *
 Copilot** can. **Antigravity, Grok and Cursor** cannot — they read a file in the directory — and
 **Muse** reads neither, which is the third route below.
 
-**Cursor is the one entry with a gap rather than a mechanism**: it reads `.cursor/mcp.json`, and
-nothing writes that file for you yet ([#2066](https://github.com/receptron/mulmoterminal/issues/2066)),
-so a cursor cell today reaches whatever MCP you configured yourself.
+**Cursor is half of each**, and the half nobody would guess is the second: it reads a file in the
+directory as agy does (`.cursor/mcp.json`, written by `server/agents/cursor-mcp.ts`), but it starts
+that MCP server on a CURATED ENVIRONMENT rather than its own — so the group and the port travel as
+ARGV, as muse's do, and the SESSION is resolved through `/api/mcp-resolve`. An agy-shaped entry (group
+in `env`, port inherited) was tried first and reached the bridge with no port at all. Cursor also refuses to
+load a server it has not APPROVED and says nothing when it skips one, so each entry is approved with
+`cursor-agent mcp enable` as the cell starts.
 
 
 | | Workspace cell / single view | Project-directory grid cell |
@@ -1487,34 +1491,37 @@ Which route a session takes is decided by `carriesFullGuiMcp()` in
 `server/session/mcp-config.ts` — the single view, a cell-less chat, or anything whose cwd **is**
 the workspace take the first; anything in a project directory takes the second.
 
-**The workspace is agent-agnostic for the agents that can RECEIVE a per-spawn config** — claude and
-codex ask the same predicate, so two terminals in the workspace reach the same tools no matter which
-of the two started them. **Antigravity, Grok and Muse cannot, and that is the exception you will
-meet first:**
+**The workspace is agent-agnostic for the agents that can RECEIVE a per-spawn config** — claude,
+codex and copilot ask the same predicate, so two terminals in the workspace reach the same tools no
+matter which of the three started them. **Antigravity, Grok, Muse and Cursor cannot, and that is the
+exception you will meet first:**
 
 | Started as | In the workspace | In a project directory |
 |---|---|---|
 | claude cell (including `?gui=0`) | `mt`, every tool | the directory's registered groups |
 | codex cell | `mt`, every tool | the directory's registered groups |
+| copilot cell | `mt`, every tool | the directory's registered groups |
+| cursor cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
 | antigravity cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
 | grok cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
 | muse cell | **the directory's registered groups** — nothing registered means **no GUI tools at all** | the directory's registered groups |
 | any launcher chip | untouched | untouched |
 
-None of the three takes an MCP flag: `agy` reads `.agents/mcp_config.json`, `grok` reads
-`.grok/config.toml` in the working directory, and `muse` reads a plugin installed for the whole
-machine — and neither a file shared by every session in a directory nor a machine-wide plugin can be
-handed to one session and not another — so there is nothing for "this cwd is the workspace" to change. The
+None of those four takes an MCP flag: `agy` reads `.agents/mcp_config.json`, `grok` reads
+`.grok/config.toml` and `cursor` reads `.cursor/mcp.json` in the working directory, and `muse` reads a
+plugin installed for the whole machine — and neither a file shared by every session in a directory nor
+a machine-wide plugin can be handed to one session and not another — so there is nothing for "this cwd
+is the workspace" to change. The
 membership is `FULL_GUI_MCP_AGENTS` in `common/guiMcpAgents.ts`, in `common/` precisely so the
 launcher form and the spawn cannot disagree about it
 ([#1423](https://github.com/receptron/mulmoterminal/issues/1423)).
 
 The consequence is easy to hit and hard to guess: `presentDocument` works in a project you once
 flipped **Canvas** on for, and is missing in the workspace where everything else is automatic. Fix it
-the same way anywhere — pick **Antigravity** or **Grok**, point WORKING DIRECTORY at that directory,
-flip the **Canvas** switch (it stays visible for both), and start a **new** session; the switch
-registers the directory, never a session already running. Full procedure:
-[Antigravity and Grok register everywhere](https://receptron.github.io/mulmoterminal/guide/en/basics.html#antigravity-gui-tools)
+the same way anywhere — pick **Antigravity**, **Grok**, **Muse** or **Cursor**, point WORKING
+DIRECTORY at that directory, flip the **Canvas** switch (it stays visible for all four), and start a
+**new** session; the switch registers the directory, never a session already running. Full procedure:
+[Antigravity, Grok, Muse and Cursor register everywhere](https://receptron.github.io/mulmoterminal/guide/en/basics.html#antigravity-gui-tools)
 · [日本語](https://receptron.github.io/mulmoterminal/guide/ja/basics.html#antigravity-gui-tools).
 
 **A launcher chip is not an agent session — it is a command.** Whatever the command line names,

package/common/guiMcpAgents.ts

@@ -1,7 +1,6 @@
 // Which agents are handed the WHOLE GUI MCP — every tool on one generated `mt` URL — when their
-// session runs in the workspace, which reach GUI tools only through what their directory
-// registered, and — a third answer since cursor landed — which reach NEITHER because the file
-// they read is one nothing here writes yet.
+// session runs in the workspace, and which reach GUI tools only through what their directory
+// registered.
 //
 // In `common/` because BOTH sides decide from it and neither can derive it: the server decides it
 // by which spawn path consults `carriesFullGuiMcp`, and the launcher form decides from it whether
@@ -58,28 +57,3 @@ export const pickCarriesFullGuiMcp = (pick: AgentPick, customAgents: readonly Cu
   if (custom) return agentCarriesFullGuiMcp(custom.agent);
   return isLaunchAgent(pick) && agentCarriesFullGuiMcp(pick);
 };
-
-/**
- * Agents that reach NEITHER route — not the per-spawn flag above, and not the directory's
- * registration either.
- *
- * Cursor alone, and that is a GAP rather than a mechanism: it reads `.cursor/mcp.json` (or
- * `~/.cursor/mcp.json`) and nothing in this repo writes either file yet (#2066). Until one does,
- * the launcher's four per-group switches cannot affect a cursor session — they register servers
- * that Antigravity and Grok read — so showing them under a cursor cell's "GUI tools" is a control
- * that does nothing, which is #1423's lesson from the other side: that issue was about HIDING the
- * only control that could have helped, and this is about SHOWING one that cannot.
- *
- * Delete this the day #2066 lands. It is a list of one because the condition is a missing writer,
- * not a property of the CLI.
- */
-export const DIRECTORY_MCP_BLIND_AGENTS = ["cursor"] as const;
-
-export const agentReachesNoGuiMcp = (agent: SessionAgent): boolean => DIRECTORY_MCP_BLIND_AGENTS.some((candidate) => candidate === agent);
-
-/** The same question asked of an Agent Picker choice. A custom agent runs Claude Code, which is on
- *  the per-spawn route, so it is never blind. */
-export const pickReachesNoGuiMcp = (pick: AgentPick, customAgents: readonly CustomAgent[]): boolean => {
-  if (customAgentFor(pick, customAgents)) return false;
-  return isLaunchAgent(pick) && agentReachesNoGuiMcp(pick);
-};