#43 Installer: add --llm param to target Claude, Gemini, or other providers

[Anonymous]

Originally created by: kumaakh

Problem

apra-fleet.exe install --skill currently hardcodes Claude as the target — it installs the MCP server config into ~/.claude/settings.json and copies the PM skill to ~/.claude/skills/pm/.

With multi-provider support, the PM itself can run on Gemini (or Codex, etc.). The installer needs to support installing into the correct provider's config and skill directories.

Proposed

Add an optional --llm CLI parameter to the installer:

# Install for Claude (default, current behavior)
apra-fleet.exe install --skill

# Install for Gemini
apra-fleet.exe install --skill --llm gemini

# Install for Codex
apra-fleet.exe install --skill --llm codex

What changes per provider

Step	Claude	Gemini	Codex
MCP server config	~/.claude/settings.json	~/.gemini/settings.json	~/.codex/config.toml
Skill directory	~/.claude/skills/pm/	~/.gemini/skills/pm/	TBD
Trust/permissions	Claude settings format	"trust": true in mcpServers	TBD

What stays the same

• Binary installed to ~/.apra-fleet/bin/
• Hooks, scripts, data directories
• MCP server binary path and stdio protocol

Notes

• Default --llm is claude for backwards compatibility
• The PM skill content (SKILL.md, templates, etc.) is provider-agnostic — only the install location changes
• Line 122 of SKILL.md says "PM always runs on Claude" — this should be updated to be provider-neutral

[Anonymous]

Ticket changed by: kumaakh

• status: open --> closed