Changelog
Every tagged Chime release, newest first — condensed from the realGitHub release notes.
Live preview: open a dev server on your laptop, from your phone
Run `chime preview --port 5173` next to your dev server and a card lands in the thread on your phone — tap it and the page renders right there, fetched over the same end-to-end-encrypted channel your messages use. No public URL, no inbound port, no tunnel provider; the relay never learns a port, a path, or a byte of the page. Grants are minted only on the machine, cover only the ports you named, expire on their own, and can be killed from Settings or the CLI. Live preview is on in the release binaries and the Android APK; it needs a WebSocket relay (the managed relay qualifies), it renders built or static apps rather than Vite's dev server, and there is no live reload yet.
Live preview tunnel (Phase 0 + A, opt-in build)
A groundwork release: the transport that would later let a phone reach a dev server on your laptop — a non-durable `eph` envelope class on the relay, a frame codec and stream machine written once in Go and once in TypeScript against a shared fixture, a loopback-only proxy on the machine, and `chime preview` port grants. It shipped behind a compile-time flag that was OFF in every binary and APK in the release, so nothing was user-visible yet. Alongside it: read receipts that arrive before a send settles are no longer dropped, and a long-poll handler that ignored client hangups stopped leaking goroutines and hanging the test suite.
OpenClaw integration, lossless local delivery, and a real chime.sh
Agents running under OpenClaw can now be woken across turns by a single gateway-owned Chime listener instead of a watcher per turn, and the MCP server speaks both stdio framings so it drops into any host. Local delivery became provably lossless: an explicit consumer-ack protocol requeues anything a closing connection didn't take, so ✓✓ now means read rather than written. chime.sh grew up too — an Astro rebuild with real docs, a changelog, a blog, a one-line install script, and npm packages wired for provenance publishing.
Dispatch: launch an agent from your phone, and it reaches you back
This release finishes the agent launcher from v0.6.0: a dispatched agent now actually receives your task through each harness's real persistent-interactive route, launches autonomously in already-trusted directories, gets its own distinct thread per launch, and is told in-band to open a Chime receiver so you can reply from anywhere. A round of code de-bloat also shipped alongside it.
Launch an agent from your phone
The headline feature: a new-chat agent launcher lets you start a coding agent on your machine straight from the Chime app — pick the agent, the working directory, and a seed task, and it spawns over the end-to-end-encrypted channel, fenced by a working-directory allowlist and argv-only exec (no shell). The conversation UI gained an agent-info panel, on-device voice-to-text shipped, and chime.sh was redesigned with a beta-signup capture.
notification & touch-interaction polish
A quirk-fix release: a new thread now appears immediately on cold launch instead of waiting for a manual pull-to-refresh, the notification tray stops piling up, a force-killed app's push notification gets its sound back, and message bubbles gained a proper long-press menu (Reply, Select, Info) with live, zero-knowledge message diagnostics.
Onboarding polish, friendly aliases & push that reaches a closed app
Android push now reaches a fully force-closed app with a content-free native notification, closing the last gap in delivery. The daemon gained a rich HTML pairing card, chime.sh/p/<code> links now land on a helpful pairing page instead of a 404, legacy aliases were migrated to friendly names automatically, and the relay's admin dashboard picked up a second tier of observability metrics.
Rich cards, friendlier identity, reply threading
Approval cards grew into A2UI, a small whitelisted declarative UI surface — tapping a choice now collapses the card in place instead of posting a fake chat bubble. Agents can send a Markdown or HTML artifact for you to review safely (sanitized Markdown, sandboxed HTML). Threads got human-friendly names like wry-otter-42, a real notification sound shipped, and you can now reply to a specific message with a quoted snippet.
reliable delivery
Rooted in a live debugging session, this release fixed message delivery end to end: inserts became idempotent and time-ordered so redelivery never duplicates or reorders a thread, a foregrounded app now fully drains its backlog instead of trickling in one message per push, the relay started sweeping unacknowledged messages past a 7-day TTL, and a half-open WebSocket keepalive fix eliminated a case where the daemon looked connected but inbound messages stalled for minutes.
observability, diagnostics, iOS, Android push, menu bar
This release added real observability: content-free relay metrics, an opt-in redacted diagnostics export on the phone, and a `chime diagnostics` command on the daemon side. iOS joined Android as a supported client, Android gained background push wakeups over FCM, and the macOS menu bar grew Pause/Resume and a Preferences menu. A live device gauntlet caught and fixed a push-related crash-on-launch before it shipped.
Pairing redesign, single binary, QR pairing & on-device observability
Pairing was redesigned around one direction — run `chime pair` on your computer, then enter or scan the 6-digit code on your phone — with a real scannable terminal QR and machine-name verification as the anti-MITM check. The Go binaries collapsed into a single `chime` executable, a first-run onboarding flow shipped, and both the relay and the daemon gained structured, zero-knowledge observability logging.
Managed relay (Durable Objects + WebSocket Hibernation)
Chime's relay moved onto Cloudflare Workers and Durable Objects, with WebSocket Hibernation as the primary transport and HTTP long-poll as a fallback — replacing a hand-run relay process that could orphan your pairing if it stopped. The phone app and daemon gained matching WebSocket clients with reconnect/backoff, plus a content-free push gateway (APNs/FCM) and a round of pairing and chat fixes.
Phase 1: working machine-hub Chime
The first working version of Chime end to end: a relay, a per-machine daemon, the CLI and SDK, an MCP server, Go-to-WASM crypto for the browser, and a Capacitor phone app with a debug Android APK. The whole machine-hub architecture existed and worked, before most of the reliability and UX polish that followed.
Full release notes and every download: github.com/charlesverdad/chime/releases