Skip to content
Cockpit0.29.0
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 monitor

Everything that happens around this repository, followed in one stream: mesh sessions, claims, handovers and reviews on every linked machine, the executor's merges and failures, and GitHub's pull requests and runs, with what is addressed to you marked

What it is

read only

Everything that happens around this repository, followed in one stream: mesh sessions, claims, handovers and reviews on every linked machine, the executor's merges and failures, and GitHub's pull requests and runs, with what is addressed to you marked

Identity
executable.monitor
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 monitor
Workflow
just monitor
MCP tool
—
HTTP
—
Declared in
apps/majordomus-cli/src/cli.rs
Capability
—

Arguments

argumentvalues fromrequiredhelp
--follow—Keep following: ask again every `--interval` seconds and print only what is new
--after—Start after this cursor (a page's `cursor`), instead of the newest signals
--limit—At most this many signals per page (default 50, at most 500)
--sources—A comma-separated subset of mesh, executor and github (default: all three)
--for—Your names, comma-separated (a worker such as 1b, a role, a login): what names them is marked for you; default $MAJORDOMUS_MONITOR_FOR
--since—How far back the first page reaches: seconds, or a number with s, m, h or d (default 1h)
--match—Keep only signals whose summary contains this text (case-insensitive)
--count—Stop following after this many signals
--until—Stop following at the first signal of this kind (e.g. merged, review_requested, run_failed)
--timeout—Give up following after this long, exiting 10: seconds, or a number with s, m, h or d
--interval—Seconds between two asks while following
--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