Skip to content

mxr daemon

Generated from mxr daemon --help. Edit the clap definitions in crates/daemon/src/cli/ and re-run npm run build in site/ to regenerate.

Start the daemon explicitly

mxr daemon [OPTIONS] [COMMAND]
Subcommand Purpose
dial-stdio Pipe raw bytes between stdin/stdout and the local daemon’s Unix socket (the Docker connhelper model). Lets any transport that can exec a process and pipe stdio reach the daemon — for example ssh -T host mxr daemon dial-stdio or docker exec -i <container> mxr daemon dial-stdio. The caller still needs local Unix-socket access on the daemon’s machine, so this adds no new trust surface
help Print this message or the help of the given subcommand(s)
Flag Description
--foreground Run in foreground (for debugging / systemd)
--stdio Serve exactly one connection over stdin/stdout (LSP/inetd model) and exit when it closes. For agent embedding and socket-activation-style supervision. Frames own stdout; logs go to file only. Cannot run alongside a socket daemon
--no-bridge Disable the HTTP bridge for this daemon run, regardless of config
--bridge-port <BRIDGE_PORT> Override the bridge port. Useful for tests and ephemeral bridges
-h, --help Print help

Start the daemon explicitly for debugging or process managers.

Terminal window
mxr daemon --foreground
mxr daemon --no-bridge

Pipe raw bytes between stdin/stdout and the local daemon’s Unix socket (the Docker connhelper model). Lets any transport that can exec a process and pipe stdio reach the daemon — for example ssh -T host mxr daemon dial-stdio or docker exec -i <container> mxr daemon dial-stdio. The caller still needs local Unix-socket access on the daemon’s machine, so this adds no new trust surface.

Same-machine assumptions degrade over remote links: the $EDITOR compose flow, attachment paths, and daemon autostart all target the daemon’s host, not your terminal. Intended for scripting and agent use.

mxr daemon dial-stdio
Flag Description
-h, --help Print help (see a summary with ‘-h’)