houmao-agent-inspect

To inspect tmux screen posture without mutating state, recover agent identity via agents list, use state/detail for precise tmux targeting, and apply the read-only screen lane to capture visible TUI state.

Agent discovery requires an evidence ladder that first recovers identity via agents list/state, optionally checks gateway/status for precise targeting, then selects the read-only artifacts lane to list stable manifest-backed runtime files without altering lifecycle.

Yes, you can inspect mailbox posture and durable turn logs for paired HTTP control scenarios by routing through the read-only mailbox and logs inspection lanes after confirming agent liveness and identity via agents state.

No, agent orchestration inspection is strictly read-only. It applies guardrails against guessing targets to verify liveness, TUI posture, mailbox state, logs, and runtime artifacts without mutating the agent lifecycle or sending mailbox messages.

The best way to verify agent liveness and TUI state is to use the discovery and screen inspection lanes, which guide you to recover identity first and capture the exact tmux pane target without triggering side effects.

Agent inspection requires an evidence ladder because strict guardrails prevent guessing targets. You must first recover identity via agents list/state, then use state/detail and gateway/status to ensure precise, safe, read-only tmux targeting.