kg-bus

name	kg-bus
skill_type	skill
description	The federated agent-to-agent bus — let this session discover and message other Claude/LLM sessions (any provider/host) and dispatch objectives to the fleet through one graph-os hub. Use for cross-session/host coordination — "who's online", "message that agent", "dispatch this to the fleet", "subscribe to a topic".
license	MIT
tags	["graph-os","messaging","bus","a2a"]
tier	core
metadata	{"author":"Genius","version":"0.1.0"}

kg-bus

Condensed intent-surface note (Seam 8). Under the default intent surface (MCP_TOOL_MODE=intent), graph_bus is held back from the default tool list (nothing removed — REST + _execute_tool still reach it exactly as documented below). Two ways to use this skill unchanged: (1) load_tools(tools=["graph_bus"]) once per session (as below), then proceed exactly as documented; or (2) call the act intent verb with the same natural-language request — the resolver routes to graph_bus for you and returns the result plus a routing justification. Set MCP_TOOL_MODE=condensed/verbose/both to expose the granular tools eagerly instead.

graph_bus (CONCEPT:AU-ECO.bus.agent-to-agent-bus) is the durable, cross-host agent bus (state lives in the KG). Actions: register/heartbeat/leave/status, roster (discover peers + presence), send (sender+payload+to|topic), receive (+since cursor), subscribe/unsubscribe, ack, dispatch (hand an objective to the fleet as a Loop). Mesh/federation: register_hub/list_hubs/federate/federate_in. Store-and-forward + auto-presence: any action keeps you online and rosterable.

Invoke

• MCP: load_tools(tools=["graph_bus"]), then graph_bus(action="roster", online_only=true).
• REST twin: POST /graph/bus with {"action": "send", "sender": "me", "to": "peer", "payload": "..."}.

Example

graph_bus(action="dispatch", sender="me", objective="Reingest the fleet", kind="develop", priority="high")