Yobiru 0.5.0 — tracked requests, receipts and final results

Yobiru 0.5.0 adds durable request receipts, progress, final results and timeout queries across your agents. Notifications remain one-way.

• Send tracked work with request send PEER/AGENT "task". The receiver records a receipt before acknowledging delivery. Agents report running and a final completed, failed, rejected or blocked result before ack.
• Query request status ID --refresh --json. A timeout means the actual outcome is unknown; it never silently cancels or reruns a task. Verified late results remain available.
• Receipt and result delivery is durable and retried with the same response ID. Replies cannot trigger reply loops. Final-result attachments keep their original snapshot.
• Expired requests cannot start through retries or manual wake. Status queries and response routing verify the original peer and agent.

Upgrade the plugin, durable runtime and installed Codex bridge together, then restart the receiver. Keep the existing data home, fixed session, adapters and permission settings. Custom dispatchers are preserved: merge the new request-handling section from CODEX_DISPATCHER.md and grant only the documented writable request-state directory. Automatic business replies still require the owner's local authorization; an upgrade does not enable them globally. A disabled Codex reply policy returns a minimal blocked protocol result.

Both endpoints need request-lifecycle-v1. An older receiver is rejected before a tracked send; use explicit --legacy-request only when intentionally accepting the old, untracked behavior, such as bootstrapping an upgrade.

Validation: 220 plugin/core tests and 146 bridge/resident/installer tests (366 total), including real isolated HTTP receivers, restart/retry, authentication, timeout/late-result, file-snapshot and unpacked-plugin cases. Python 3.12 runtime; Python 3.8 syntax compatibility checked. These checks do not establish native macOS/Grok Bot operation, guaranteed model execution or exactly-once task execution. See docs/VERIFICATION.md for evidence bounds.

Release archives and SHA256SUMS are attached. Installation and migration guidance is available in the English, Chinese and Japanese READMEs and the bundled upgrade skill.

Yobiru 0.4.4 — service stability and transport diagnostics

Fixes

• Stable service Python paths (#9, fixes #7): receiver and update-reminder templates preserve interpreter symlinks and virtual environments. For a reported Homebrew Cellar executable, a verified same-file stable path within the same prefix is used when available. Explicit receiver --python overrides remain unchanged.
• Actionable transport diagnostics (#10, fixes #8): timeouts and connection errors include the peer, resolved endpoint and a bounded tailscale ping suggestion. Send failures include the message ID and explain that delivery is unknown; check the recipient's inbox before sending again. There is no automatic retry or Tailscale restart. Local file errors remain distinct, and malformed HTTP response contents are excluded from diagnostics.

Upgrading

Update the plugin, install its durable runtime with install-runtime --upgrade --apply, and restart the receiver. If the Codex bridge is installed, follow the upgrade skill with the same session UUID, socket and Codex home. Preserve existing data, agents, webhooks, permissions and custom instructions.

Existing service definitions are not rewritten automatically. On macOS, regenerate and reload the receiver definition with service-template launchd and any installed reminder definition with update reminder-template launchd (retain --retry-notices if used). Review the interpreter and plugin script paths before loading them. The separate macOS Codex bridge installer is outside this service-template fix.

Verification

The release tree passed 191 plugin tests and 132 bridge/resident/installer tests. Packaging consistency, deterministic archives, private-data checks and Python 3.8 syntax parsing passed.

Homebrew regression tests simulate an upgrade and old-keg cleanup on Linux and execute saved interpreter paths; a real isolated virtual environment is also covered. Native macOS/launchd upgrades and the reported stale Tailscale/DERP path were not reproduced. The transport tests include a real loopback receiver accepting a message and withholding its response.

yobiru 0.4.3 — current-IP routing after device rebuilds

Yobiru 0.4.3 fixes short-name routing after a Tailscale device is rebuilt or reinstalled.

• Each new send resolves the latest Tailscale status. A short name matches the DNS short name or reported HostName; the unique online match takes precedence over old offline records.
• Ambiguous names now produce an error with exact candidate names instead of routing by list order.
• Sending, device discovery (agents --peer), and explicit upgrade notices share the same lookup rules. Full MagicDNS names and explicit IPs remain exact targets.
• Updated the send skill and English, Chinese, and Japanese documentation.

Use a stable device name rather than a saved IP for routine messages. After rebuilding a cloud computer, restore its chosen Tailscale hostname and start its receiver. This update does not restore a lost login, move old attachment permissions or historical replies to a different identity, or add offline retries for ordinary messages.

Upgrade

Update the Codex/Cursor/Grok Bot plugin, or download the plugin ZIP and verify SHA256SUMS. Then run install-runtime --upgrade --apply from the new package and restart the receiver. If a Codex bridge is installed, reinstall it with the same thread UUID and existing configuration. Preserve data, session identities, access policy, wake adapters, and reply permissions.

Upgrade instructions.

Validation

The release passed 172 plugin tests (including 19 name-resolution regressions), 132 bridge/resident/installer tests, package consistency and private-marker checks. Tests cover IP changes, old offline nodes, name collisions, agent routing and preserved exact identities. The regression suite uses injected Tailscale snapshots and isolated HTTP peers; it does not claim a live Grok Bot rebuild or native Windows/macOS validation. Wire protocol v1 and access policies are unchanged.

yobiru 0.4.2 — resident dispatcher and CLI reliability fixes

Yobiru 0.4.2 fixes three issues reported against 0.4.1.

• Linux resident dispatcher: the bridge daemon keeps its existing Codex session connected and resumes the same session after reconnecting. A separate resident status distinguishes subscription from queued or completed work. Resolves #1 via #6.
• Dispatcher sandbox setup: documents the minimum inbox/handled write permissions, optional attachment outbox access, and networking for authorized replies. Existing session permissions are preserved. Resolves #2 via #5.
• Non-UTF-8 output: the CLI no longer crashes on Chinese text or emoji in cp1252/ASCII pipes. JSON preserves Unicode values; message transport and storage remain UTF-8. Resolves #3 via #4.

Upgrade

Update the Codex/Cursor/Grok Bot plugin, or download the plugin archive below and verify it against SHA256SUMS. Then use the new package to run install-runtime --upgrade --apply and restart the receiver.

Linux Codex bridge users must also reinstall the bridge using the same thread UUID, Unix socket and Codex home. Keep your existing session, data, access policy and wake/reply permissions. Check codex-bridge status for resident.state: connected; a connection does not by itself prove task completion. See the upgrade skill and sandbox guide.

Validation

The combined tree passed 153 plugin tests, 132 bridge/resident/installer tests and 59 real Tailscale single-host checks. Package consistency, reproducible archive tests and private-marker checks passed. Encoding tests used real cp1252/ASCII pipes on Linux, not native Windows. Resident tests include isolated WebSocket lifecycle tests and real Codex app-server probes; they do not claim a completed real model task.

No wire-protocol change or automatic access-policy migration.

yobiru 0.4.1 — consistent icon and plugin branding

The yobiru icon now matches yobiru.com: two small black eyes in the rounded lower head of the orange spirit.

• Codex and Cursor/Grok Bot plugin packages use the same approved PNG; the Codex accent matches the website.
• English, Chinese and Japanese READMEs, the plugin README, and the illustrated demo use the new branding.
• Removed the old blue SVG and its generator to prevent it from returning in future builds.

This is a branding and packaging patch. Messaging, files, access policies, wake-ups and sessions retain their 0.4.0 behavior; only the reported product version changes.

Validation: all 16 existing packaging tests passed, including the Codex manifest validator, archive completeness and reproducibility. tools/build_plugin.py check passed. Both ZIPs include the same icon as the website. Historical 0.4.0 runtime verification remains documented in docs/VERIFICATION.md.

For an existing Codex marketplace installation:

codex plugin marketplace upgrade yobiru
codex plugin add yobiru@yobiru

Cursor/Grok Bot users can update their plugin or use the attached plugin ZIP. Existing installations show the new icon after their host refreshes the plugin cache. This release does not migrate data, restart receivers or send tasks to other machines.

Download either the plugin or marketplace archive and verify it against SHA256SUMS.

yobiru 0.4.0 — tailnet access policy and upgrade recovery

Yobiru 0.4.0

• New installations accept authenticated Tailscale peers by default, subject to Tailscale network access and local deny rules. Restricted allowlist mode remains available.
• Existing allowlists remain active until a backed-up, explicit policy set --mode tailnet --apply migration. Access policy changes take effect on the next receiver or bridge authorization check.
• Deny rules cover messages, discovery, attachment access and pending wake attempts. Wake caps, session bindings, reply permissions and recipient-bound file tokens remain independent.
• update maintain --apply records release reminders and recovers previously queued upgrade notices after restart or offline periods. reminder-template --retry-notices prints an opt-in 15-minute/startup schedule.
• Notification retries retain their original identity and recipient. Unknown outcomes, damaged saved routes and revoked access do not cause blind resends.
• English, Chinese and Japanese documentation includes the 0.4 migration procedure.

No wire-protocol change, automatic remote installation, general offline message queue or centralized storage service is introduced. Existing receivers and Codex bridges must be upgraded before policy migration. Install the printed maintenance schedule explicitly and regenerate it after plugin upgrades.

Validation: packaged/loopback tests, Codex bridge and installer tests, package consistency/privacy checks, and 59 real Tailscale checks on one host. Multi-device rollout and operating-system timer installation are not part of this release preparation.

yobiru 0.3.0 — Setup, resident sessions and coordinated upgrades

Yobiru 0.3.0 helps agents set up their Tailscale connection, identify the session receiving their messages, and coordinate upgrades across their known installations.

• Guided onboarding for Linux, macOS and Windows, including missing Tailscale, sign-in, receiver setup and delivery adapters.
• Authenticated agent discovery with receiver versions, resident session IDs, and clearly labeled native session names, confirmed titles and aliases.
• Official release checks, optional weekly reminder templates, and durable upgrade notices with wake requests, offline pending state and deduplication.
• Six plugin skills, with setup and upgrade guides in English, Simplified Chinese and Japanese.

Upgrading

Update the plugin, then use the new package to run install-runtime --upgrade (review the plan, then add --apply) and restart the existing receiver. If installed, upgrade the Codex bridge using its same fixed session UUID. Keep the existing data directory and permissions. See the upgrade guide.

Plugin updates do not replace a separately installed receiver. Upgrade notices indicate delivery; a later authenticated version check verifies the running software. They do not authorize remote actions.

Validation

109 plugin tests and 113 bridge tests passed, including isolated loopback integration tests. Package consistency, reproducible archives and private-data checks passed. Python 3.8 syntax was checked statically; runtime tests used Python 3.12. Platform guidance and live cross-machine operation are not covered by the offline test suite.

Use yobiru-0.3.0-plugin.zip for a standalone plugin, or yobiru-0.3.0-marketplace.zip for the repository marketplace layout. Verify downloads against SHA256SUMS.

yobiru 0.2.1 — Preserve existing agent workflows on upgrade

Existing Tailmsg deployments can migrate without sending specialized message types into the general Codex dispatcher or losing locally customized settings.

• Adds optional message-kind exclusions and a trusted local handler, shared by macOS and Linux. Inbox validation happens before routing; scans and queued retries honor the same exclusions.
• Bounds handler execution beneath the receiver timeout and cleans up the handler process group. A started handler is not automatically replayed after an uncertain failure; the inbox stays pending and the receiver log records the outcome.
• Preserves installed dispatcher instruction contents, authorized replies, CLI paths, timing, and routing settings during upgrades. Dry runs validate the merged configuration; rollback retains original instruction bytes.
• Updates English, Chinese, and Japanese documentation and plugin bundles.

Validation: 108 bridge/client/installer tests and 55 plugin tests passed. Private-information checks and deterministic archive builds passed. Release tests use isolated homes, fake services, and temporary sockets; live host migrations are separate operational acceptance, not a claim of universal platform compatibility.

The receiver protocol remains tailmsg v1, and existing data homes and fixed Codex sessions remain compatible. The plugin and marketplace archives below include SHA-256 checksums.

yobiru 0.2.0 — Linux Codex wake bridge

yobiru now supports waking one existing Codex session on Linux through a local app-server Unix socket. The same plugin and durable inbox/queue are shared with the existing macOS bridge; no central service or new UI is required.

• Adds Linux user-systemd installation, true dry-run, file-only installation, upgrades, status diagnostics and rollback.
• Keeps the dispatcher, Codex account directory, reply settings and queued messages stable across upgrades. Refuses conflicting installations and unsafe rollback.
• Detects missing or stale sockets before sending; reconciles uncertain delivery without blind retries.
• Updates the English, Chinese and Japanese READMEs, setup/wake skills and platform documentation.

Validation: 71 bridge/installer tests, 55 plugin tests, and six independent acceptance groups against the extracted plugin passed. Build consistency, reproducible archives and checks for personal network addresses and secret markers passed.

Linux requires an existing Codex app-server, its same-user local Unix socket, an existing session UUID and a user systemd manager. This release was verified with isolated sockets, substitute CLIs and service managers; live Codex processing and two-machine end-to-end delivery were not tested for 0.2.0. A queue receipt means accepted, not completed.

See the README for setup and docs/VERIFICATION.md for the verification boundaries. The plugin archive is suitable for folder-based installation; the marketplace archive includes both Codex and Cursor catalogs. SHA256SUMS covers both archives.

Yobiru 0.1.0

Yobiru 0.1.0

Let your personal agents talk to each other over Tailscale. Yobiru carries messages, structured data, files, and receiver-controlled wake-ups between your own computers and cloud workspaces.

• One portable package with four skills, a Python CLI, and Codex / Cursor plugin manifests.
• No Yobiru account or central message/attachment storage service.
• Complete English, Chinese, and Japanese guides, including an AI-generated conceptual demo.
• MIT licensed. Existing tailmsg protocol v1 deployments remain compatible.

Install in Codex

codex plugin marketplace add chekusu/yobiru
codex plugin add yobiru@yobiru

Start a new conversation and ask Yobiru to check your setup. Python 3.8+, Tailscale, receiver allow lists, and running receivers are required; installation alone does not configure networking or start services.

Downloads

• yobiru-0.1.0-plugin.zip: the portable plugin directory.
• yobiru-0.1.0-marketplace.zip: the plugin plus both repository marketplace catalogs.
• SHA256SUMS: checksums for both reproducible archives.

Verification and early-release status

52 plugin tests, 42 Codex bridge tests, the Codex plugin validator, and 59 real-Tailscale checks passed. The real-network checks use temporary receivers on one Linux host; they do not establish cross-machine acceptance. Repeated archive builds are byte-for-byte identical.

Codex installation and skill discovery have been tested locally. Cursor, Grok Bot, DOTS, and cross-platform end-to-end collaboration still require real-host verification. No verified DOTS connector is included. Public plugin marketplace listings have not been submitted or approved. See the verification notes.

The public source snapshot and these archives were checked for credentials and private network identifiers before publication. Private development history and runtime state are excluded.