Files
multi-agent-mux/.agents/skills/multi-agent-mux-orc-onboard/SKILL.md
T
GodopuandClaude Opus 5 508ca99d71 docs(issue-5): phase 1 benchmark results, contract mapping, task checklist
Records the measured numbers and syncs every document that names the
delegation script paths, then bumps the framework to 4.3.0 in the three-way
lockstep (lib.sh, VERSIONS.md current + matrix, eight SKILL.md frontmatters).

phase1-benchmark.md carries both arms. The deterministic fake transport is what
CI asserts on: 50 publishes cost 50 connections one-shot and 1 persistent, p50
54.813ms -> 0.002ms. The real broker run is informational, since the PoC
default is a public broker: p50 1892.728ms -> 275.992ms, about 85% off.

It also corrects the plan's own estimate rather than repeating it. D8 predicted
the new shell path would drop from 3 forks to 2; the implementation is still 3,
because keeping the `_delegate_script publish_event.py` lookup is the only
thing that produces the "missing script tree does nothing" non-fatal contract
that C-02 pins. Saving that fork would change the contract, so it is deferred
to phase 4 rather than taken quietly.

SKILL.md gains the context table saying which tree wins where, so an operator
reading it knows a frozen loop runs frozen delegation code. The script paths in
every document remain correct and every quoted command still works verbatim.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UrDNJkHmm18uu7n7JwV5Qd
2026-09-06 15:48:38 +09:00

2.4 KiB

name, description, version, author, license, platforms, environments, metadata
name description version author license platforms environments metadata
multi-agent-mux-orc-onboard Register current or specified orchestrator session UUID into agent-sessions.yaml orchestrator_uuids list to prevent sub-agent discovery capture. 4.3.0 godopu MIT
linux
macos
terminal
herdr
hermes
tags related_skills prereq_skills
agent
herdr
claude
antigravity
agy
hermes
grok
opencode
codex
orchestrator
onboard
isolation
multi-agent-mux-create
multi-agent-mux-resume
multi-agent-mux-monitor
multi-agent-mux-create

multi-agent-mux-orc-onboard

Registers an orchestrator session UUID into the orchestrator_uuids list of .mam/agent-sessions.yaml (and underlying state DB). This ensures that find_workspace_uuid and verify_session_uuid in lib.sh exclude orchestrator conversations when discovering unassigned sub-agent session UUIDs.

Usage

.agents/skills/multi-agent-mux-orc-onboard/scripts/orc_onboard.sh [OPTIONS]

Options

  • --uuid <uuid>: Explicitly register the specified orchestrator session UUID.
  • --remove <uuid>: Remove the specified UUID from the orchestrator_uuids list.
  • --list: Display all currently registered orchestrator UUIDs.
  • --no-autodetect: Disable process ancestry auto-detection when --uuid is not provided.
  • --dry-run: Output proposed changes without mutating the state registry.

Auto-Detection Hierarchy (Rev.2)

When --uuid is omitted, orc_onboard.sh inspects the process ancestry tree of the nearest agent ancestor (claude, agy, hermes, grok, opencode, codex) in the following order:

  1. CLI argv:
    • claude -r <uuid> / claude --session-id <uuid>
    • agy --conversation <uuid>
    • grok --session-id <uuid> / grok --resume <uuid>
    • opencode --session <uuid>
    • codex resume <uuid>
  2. Family-Matched Environment Variables:
    • claude → CLAUDE_CODE_SESSION_ID
    • agy → ANTIGRAVITY_CONVERSATION_ID
    • hermes → HERMES_SESSION_ID
    • grok → GROK_SESSION_ID
  3. Fallback:
    • If no valid ID matching the nearest agent family is found, exits with status 3 (Could not detect orchestrator ID).

Exit Statuses

  • 0: Success (registered, removed, listed, or already present).
  • 1: Conflict — the ID is currently owned by a running sub-agent session row.
  • 2: Invalid arguments or malformed ID format.
  • 3: Detection failed — ID could not be determined.