https://romnn.github.io/micromux/docs/agent-control/Recent content in Agent control on micromuxHugoen-ushttps://romnn.github.io/micromux/docs/agent-control/control-plane/Mon, 01 Jan 0001 00:00:00 +0000https://romnn.github.io/micromux/docs/agent-control/control-plane/<h1 id="the-control-plane">The control plane<a class="anchor" href="#the-control-plane">#</a></h1> <p>The control plane is the local endpoint every running <code>micromux</code> opens. The TUI, the MCP server, and the <code>micromux ctl</code> client all speak to it, so any of them can inspect and steer a session with identical semantics.</p> <h2 id="micromux-ctl"><code>micromux ctl</code><a class="anchor" href="#micromux-ctl">#</a></h2> <p><code>ctl</code> is the shell client — the same control plane an agent uses, dogfooded from your terminal. It targets the session for the config resolved from the current directory (or one you name with <code>--session</code>).</p>https://romnn.github.io/micromux/docs/agent-control/dynamic-services/Mon, 01 Jan 0001 00:00:00 +0000https://romnn.github.io/micromux/docs/agent-control/dynamic-services/<h1 id="dynamic-services">Dynamic services<a class="anchor" href="#dynamic-services">#</a></h1> <p>Beyond the services declared in <code>micromux.yaml</code>, the control plane can create <strong>runtime (dynamic) services</strong> — processes an agent starts on the fly, for example to run a one-off script or bring up a helper alongside your stack. They are <strong>disabled by default</strong> and bounded by an explicit policy, because a runtime service is a same-user command with real blast radius.</p> <h2 id="enabling-them">Enabling them<a class="anchor" href="#enabling-them">#</a></h2> <p>Runtime services are off until you opt in, in the target session&rsquo;s config. The policy is <strong>latched when the session starts</strong>, so changing it requires a session restart:</p>