Whether cloud (MuxBus) messages are reaching this channel’s agents, made
visible: a sign-in that stops working, or a relay that can’t be reached,
used to leave nothing but a log line while agents silently stopped getting
review, CI and cross-machine messages.
Publish this install’s presence record to the account’s relay, so a
signed-in phone off the LAN can list it (agentmux-mobile’s
SPEC_FLEET_HOST_TAGS_AND_CLOUD_HOSTS_2026_10_06 §6.3).
Publish each agent’s WAN key to the account’s cloud key directory,
certified by this install’s instance key
(SPEC_WAN_JEKT_VERIFICATION_2026_09_24.md §2.2, step D1b).
Identifier MuxBus’s single global credential set is registered under
with both the broker scheduler (crate::broker) and the OS keychain
(backend::storage::muxbus’s secret_store key) — deliberately the same
string in both places so the two are trivially correlated in logs.
Why the stored AgentMux Cloud sign-in can’t work anymore, or None if it
still can (docs/specs/SPEC_CLOUD_SETTINGS_DISCOVERY_2026_09_27.md §3.3).
Stale means only a new sign-in helps: