chekusu/yobiru
Peer-to-peer messages, file handoff and receiver-controlled wake-ups between AI agents on your own Tailscale network. Speaks the tailmsg protocol v1; no central server.
Read and process this machine's Yobiru (tailmsg) inbox - list pending messages for an agent, show one, fetch and verify attachments, reply, and acknowledge when done. Use when woken by a Yobiru or tailmsg notification, when the user asks to check messages from other machines or agents, or to act on a pending request from another agent.
Send a Yobiru (tailmsg) message, structured data or files to an agent on another machine in the user's Tailscale network, ask for a wake-up, or reply to a received message. Use when the user asks to message, notify, hand a file to, or answer another machine's agent, for example "send this report to the codex agent on my dev server".
Show which of the user's machines and agents are online and which resident session (name and exact id) handles each agent's Yobiru messages, and bind an agent to the user's existing conversation without creating a duplicate. Use when the user asks "which agents are online", "which session handles messages", "where do my Yobiru messages go", or wants to name or find the fixed conversation for an agent.
Set up, check or repair Yobiru (agent-to-agent messaging over the user's Tailscale network, tailmsg protocol) on this machine - guided onboarding from a machine without Tailscale, sign-in, a Tailscale-based access policy and agent names, a durable receiver, how each agent is woken, session binding and verification. Use when the user says "set up yobiru", asks to install, configure, verify or repair Yobiru or tailmsg, or when another Yobiru command says "not set up".
Check for Yobiru updates from the official chekusu/yobiru releases, upgrade this machine safely (plugin, durable receiver runtime, receiver restart, Codex bridge), then notify the user's other known Yobiru installations with a versioned upgrade notice and track which ones converged. Also handles a received upgrade notice. Use when the user asks about Yobiru status, versions, updates or upgrades, sets up update reminders, or an inbox message has kind yobiru-upgrade-notice.
Configure whether and how other machines' Yobiru (tailmsg) messages wake this machine's agents - receiver-side wake policy per sender, quiet hours, rate limits, and per-agent wake adapters (a local program, a Grok Bot routine webhook, or the optional Codex bridge for macOS desktop or a Linux app-server). Use when the user wants messages to wake an agent right away, wants fewer or no wake-ups, or asks why an agent was or was not woken.