#219 bug: Gemini members launch apra-fleet.exe — should only run on orchestrator

[Anonymous]

Originally created by: kumaakh

Problem

Gemini member conversations still launch apra-fleet.exe (the fleet MCP server) as part of their session startup. This was already fixed for Claude members — member conversations no longer start the fleet MCP server; only the orchestrator (PM) conversation does.

Why it matters

A Gemini member launching its own fleet MCP server causes:

• Unnecessary process spawned on the member machine
• Potential port conflicts or state confusion if the member's fleet server collides with the orchestrator's
• Wasted resources on every Gemini member dispatch

Expected behaviour

Member conversations (Claude or Gemini) should not launch apra-fleet.exe. Only the orchestrator conversation (the one running the PM skill) should have the fleet MCP server active.

Root cause (likely)

compose_permissions writes .gemini/settings.json for Gemini members and likely includes the fleet MCP server configuration in that file — the same way Claude's CLAUDE.md used to include it before the Claude-side fix. The Claude fix was to strip the fleet MCP entry from the doer/reviewer permission profiles so member sessions don't inherit it.

Fix

compose_permissions must not include the fleet MCP server in the Gemini settings.json it writes for doer or reviewer roles. The fleet MCP entry should only be present in the orchestrator's configuration.

Related

• Parallel issue: compose_permissions writes .gemini/settings.json with UTF-8 BOM (CRITICAL backlog item) — both should be fixed together since they touch the same file generation path in src/tools/compose-permissions.ts

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed