CLIConcepts
Overview
The mental model for how the Mogplex CLI works — architecture, transports, permissions, approvals, and attach mode.
These pages explain the load-bearing concepts behind the CLI cockpit. Read them in order if you're new; jump to the one you need otherwise.
Architecture
Transport → dispatcher → store → React. Structured events only, no polling, contracts as the boundary with core.
Transports
The three transports (process, daemon, stdio) and how the router picks one.
Permissions
Two-mode permission model. Global + per-project rules layered on disk.
Approvals
How tool calls get gated, the queue, and what auto-reject means.
Attach
`--attach <runId>` to pull up a run that started somewhere else.
Pick a page by question
- "What actually happens when I press a key?" → Architecture
- "Why did the CLI pick this transport?" → Transports
- "Why is this tool call asking me / why isn't it?" → Permissions and Approvals
- "How do I see a run that started in CI?" → Attach