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 state
The state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and review
What it is
read onlyThe state every linked runtime converges on, summarised with its digest; --full for every session, claim, handover and review
- Identity
executable.mesh.state- 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 state- Workflow
just mesh-state- MCP tool
- —
- HTTP
- —
- Declared in
apps/majordomus-cli/src/cli.rs- Capability
- —
Arguments
| argument | values from | required | help |
|---|---|---|---|
--full | — | Every session, claim, handover and review, not the summary | |
--live-claims | — | Only claims that are still held | |
--after | — | Only what moved after this Lamport stamp | |
--session | — | Only this session: its key or its bare id | |
--runtime | — | Only this runtime (`<node>-<runtime>`), or every runtime of a node id | |
--kind | — | Only this collection: sessions, claims, overlaps, handovers or reviews | |
--limit | — | At most this many of each collection, the newest first kept | |
--open | — | Only what is still open: active sessions, live claims, unanswered reviews, untaken handovers | |
--matching | — | Only what mentions this text: a path, a branch, an issue, a pull request, a word | |
--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 |