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
I1997
The peer board can be read from the command line
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
0- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
0of2
Moves
plan.transitionWhat it is
- Objective
- Project the peers capability onto the command line, so that a worker with no MCP tools can still ask who else is working in this repository and on which paths.
- Why
- On 2026-10-08 the owner told a session in prismatic-platform to 'use majordomus to find other instances / peers', and the tool had nothing to answer with: `majordomus peers` is an unknown command, and `session` describes one provider session of one checkout. Cross-session awareness exists only as the MCP tools majordomus_peers and majordomus_announce. From 2026-09-12 until 0.17.0 Claude Code dropped every majordomus_* tool in this repository, because two tools published an input schema with no root type, so for a month no session here could read or write the board either; eight sessions coordinated by direct messages instead. A reading that exists on one projection only is gone when that projection is.
- Now
- peers.list and peers.announce are served over MCP and HTTP. The command line has no reading of the board; `majordomus context` prints a peers section only when the shell tool can reach the server and somebody else is attached.
- Wanted
- `majordomus peers` prints the board gathered across every checkout of the repository — each peer, its worktree, its claims, whether it is attached — with `--format json`, from the same capability the MCP tool projects. It says when a checkout's board could not be asked. In a repository with no layer or no server it says that, and exits with the code for a missing artifact rather than 0.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- `majordomus peers` lists a peer announced over MCP by another client of the same repository, with its worktree and claimed paths
- The command is a projection of the registry's capability: no board logic is written a second time for the command line
- With no server running it reports that no board could be asked and does not exit 0
- Validation
bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>- Evidence required
cli_peers_lists_an_mcp_peer_casecli_peers_without_server_case- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/capability/builtin/peers.rsapps/majordomus-cli/src/cli.rsdocs/MCP.mdtest/cases- Not
- unknown: the record declares no `non_scope`
- Depends on
- unknown: the record declares no `depends_on`
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-08
- Updated
- 2026-10-08
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
| Level | Code | Message | Reproduce |
|---|---|---|---|
| WARN | scope_conflict | shares apps/majordomus-cli/src/capability/builtin/peers.rs with I1999; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs/MCP.md with I2059; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2114; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2282; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2410; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares apps/majordomus-cli/src/cli.rs with I2411; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2412; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2413; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares apps/majordomus-cli/src/cli.rs with I2414; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2653; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2713; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2714; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2716; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2717; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2718; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares apps/majordomus-cli/src/capability/builtin/peers.rs with I2720; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2723; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares docs/MCP.md with I2731; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2734; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2740; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2742; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2747; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2760; they may not run concurrently | majordomus plan validate |
| WARN | scope_conflict | shares test/cases with I2786; they may not run concurrently | majordomus plan validate |