chekusu / yobiru

# yobiru（ヨビル）
**Let your agents talk to each other.**
Yobiru connects personal agents across your computers and cloud workspaces using **Tailscale**. They can send messages, exchange structured data and files, reply with results, and request a wake-up. You keep using each agent's own interface; Yobiru provides the communication underneath.
**English** | 简体中文 | 日本語
*AI-generated conceptual demonstration, not real screenshots or a verified end-to-end integration. Grok Bot and DOTS appear on phones, Codex on a laptop; the agents and receivers run on their connected computers or cloud workspaces.*
## Why Yobiru?
Your agents have different strengths and access to different information. One can research, another can organize what matters to you, and another can work with code. Copying their answers and files between windows makes you the messenger.
Yobiru gives those agents a small, shared way to communicate:
- **Chat across machines:** address an agent with `host/agent` and reply to its messages.
- **Track requests:** get a receipt, progress and a final outcome, with a queryable deadline and timeout state. Notifications need no reply.
- **Share useful context:** send text, JSON, reports, logs, and other files.
- **Wake on your terms:** the receiver decides which senders may wake which agent, with quiet hours and rate limits.
- **Keep your own tools:** one plugin package includes seven skills and a Python CLI, with Codex and Cursor manifests and dedicated Grok Bot setup and recovery guidance.
- **Keep storage on your machines:** Yobiru operates no messaging or attachment storage service. Files are fetched from the sender over Tailscale.
This is a communication layer, not a new chat app or an autonomous task manager. Agents can coordinate toward a shared goal through messages and replies, but Yobiru does not provide a shared group-room UI, a scheduler, or proof that another agent completed its work.
## A conversation across three agents
Imagine asking: **“What are people discussing, what matters to my project, and what should we build?”**
| Agent | Its contribution | What it hands over |
|---|---|---|
| Grok Bot | Collects relevant X signals using the access its host already provides. | A summary, source links, and `signals.json`. |
| DOTS | Relates the findings to your context and organizes a brief. | `brief.md` and questions for the coding agent. |
| Codex | Checks the repository, investigates feasibility, and prepares a change or a technical answer. | Findings, files, and a reply to the requesting agent. |
This is an illustrative workflow. Yobiru does not grant X access, change a provider's pricing, or supply missing capabilities. **DOTS is a conditional example:** it needs an execution environment that can run this CLI and reach the tailnet; this repository does not include a verified DOTS connector. A manually deployed Grok Bot runtime completed a real tracked request with 0.5.0; native marketplace installation and rebuild recovery require separate