A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
majordomus mesh status
Whether the mesh runs in this checkout's server and why not when it does not, with every provider's state and the registry's tallies
What it is
read onlyWhether the mesh runs in this checkout's server and why not when it does not, with every provider's state and the registry's tallies
- Identity
executable.mesh.status- Program
- executable
- Runs
- non interactive
- Requires
- repositorylayer
No machine surface carries this command: no capability declares this command line, so no machine surface has a typed input schema to execute from
Where it appears
- Command line
majordomus mesh status- Workflow
just mesh-status- MCP tool
- —
- HTTP
- —
- Declared in
apps/majordomus-cli/src/cli.rs- Capability
- —
Arguments
| argument | values from | required | help |
|---|---|---|---|
--repo | — | Start the search for the repository root here (default: the current directory) | |
--discovery | — | How declarative files are enumerated | |
--strict | — | Refuse to proceed when any file of the layer carries an error diagnostic | |
--share | — | The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable | |
--format | — | `text` for a person, `json` for a machine; both render the same answer |