Changelog
Each date is the day that version became publicly available: the iPhone app on the App Store, the agent on npm.
0.1.9
Agent only; the iPhone app stays at 0.1.5 for now.
Agent — 2026-11-16
Pairing works better in terminal chats. The pairing QR is smaller, so it fits narrower chat windows, and the agent now shows the pairing link first, so you can open it on the iPhone that has Syncky Health when a chat can't display the QR. The link, QR and code go only in the private reply to you and expire with the pairing. pair --show-qr shows the current pairing again without starting a new one, and pair --qr-png or pair --qr-svg saves the QR as a private image in the agent's folder, which is deleted when pairing finishes or expires. The bundled skill moves to version 11: it tells your agent how to pass on the pairing link, QR and code, adds short safety rules for every client, and says which instructions take precedence. wait no longer stops when another agent task is briefly writing local state.
0.1.8
Agent only; the iPhone app stays at 0.1.5 for now. Agent 0.1.7 was not published on npm, so this version brings its changes.
Agent — 2026-11-16
Setup needs only the agent's name. If the Relay refuses registration, the agent reports registration_refused and asks you to stop instead of retrying. Guides, skills, help and error texts describe only the App Store app and its default Relay, and pairing links follow the Relay the agent was set up with. The bundled skill moves to version 9, so agents with an older installed copy pick up the new wording. syncky_send describes the receipt it returns and how pending sends retry while receiving runs. Inbox writes scan the local index once per record, and a replaced inbox file is indexed again from the start instead of stopping the agent.
0.1.6
Agent only; the iPhone app stays at 0.1.5 for now.
Agent — 2026-11-15
MCP tools now describe every input, what each tool returns and which tool to use next. The inbox tool explains that its continuation cursor is a local position, separate from the Relay sequence used to acknowledge records, and that history is pruned after 30 days when receiving runs. Commands, messages and behaviour are unchanged. The GitHub release adds an instructions-only skill archive for ClawHub that installs the agent from npm.
0.1.5
iPhone app — 2026-11-14
Russian and Latvian are now available in the app, widgets and notifications. Home's Pick the code card resumes the pending pairing-code choice, and the reminder uses the same wording. Health selection during onboarding is shorter, and the pairing page puts the steps for an installed app first on a phone. Home explains collection errors or a first read with no records and offers the next step, including when only an agent has read access or a server has no types selected.
Health type search handles accents, spaces and hyphens more consistently. Write refusals distinguish types outside your write allowance from unsupported types. Remove this agent's Health records explains that removal covers only this agent's records in currently allowed write types. Relay deletion explains how to request erasure first and what former-member data remains; Export log explains the unmasked identifiers and other details in the file. Launch screens describe free access without implying a purchase.
Workout statistics sent to an agent exclude types outside its read access, including types it has released. Repeated access-request alerts are limited; requests remain queued for the app to fetch until they expire. Agent names and request reasons are filtered for display. Pairing confirmation gates Health uploads and queued writes, and invalid incoming commands are rejected while the existing pairing state is kept. The pairing page uses HTTPS app links without a custom-scheme redirect. Relay groups repeated setup attempts from the same IPv6 network under shared limits.
Agent — 2026-11-14
Errors now include actionable hints, and failed send receipts include the Relay cause when available. Pairing guidance explains recovery after a deleted hub and the hosted pairing limits. wait can still return a completed, currently confirmed pairing after its link expires. Access requests accept a positive lifetime up to 24 hours; guidance consistently explains the seven-day wait after a declined type and the need for renewed owner intent before another request.
Setup without initial types now walks through Choose Health data, selection, Save, Health authorization and Sync now. Inbox guidance explains that receiving prunes files older than 30 days; an idle agent does not. Replay checks use authenticated message IDs independently of Relay order, including after restart and inbox pruning. Pairing IDs and device names are checked, requests stay bound to the initialized Relay origin, and credential-bearing requests refuse redirects. Bounded inbox scans return continuation pages for large histories, and the example agent limits response sizes.
0.1.4
iPhone app — 2026-11-12
An agent can now give up Health types it no longer needs. The app removes them from that agent's access at once, without asking you, and names them in the agent's activity; your own Health selection and iOS permissions do not change. When an agent sends an invalid access request, the app tells you why. You can attach a diagnostics report to feedback you send in the app: it is off until you switch it on, and you can preview it first.
Agent — 2026-11-12
Activity totals now arrive as sums. An iPhone with app 0.1.3 or newer sends cumulative Health types (steps, energy, distances and similar) to agent 0.1.4 as 15-minute UTC sums in sync.summaries, and no longer as raw samples; a later sum for the same phone, type and interval replaces the earlier one. Food, water, insulin, inhaler use, alcoholic drinks, falls and similar logged entries stay raw samples. A deletion of data older than 7 days may leave its interval unchanged. With send --type scope_release the agent gives up Health types it no longer needs, and status reports the outcome; this needs iPhone app 0.1.4. When the agent refuses an access request before sending it, the error names the reason and the types that cannot be written. The MCP Registry entry and the MCPB bundle list the agent's tools.
HTTPS pairing links replace custom-scheme links by default. Use pair --read and --write to request initial Health types. The pairing screen lets you choose access for this agent. Access replies now explain request limits and refusals for individual types. The agent recovers home locks left after a reboot. receive keeps health records out of terminal output by default; use --emit-records only when you want them printed.
0.1.3
iPhone app only; agent 0.1.3 was not published on npm, and its agent changes are part of agent 0.1.4.
iPhone app — 2026-11-11
Improved agent setup and pairing: easier and more reliable. You can now choose Health access during pairing. Pairing links open the app over HTTPS; when it is not installed, the page offers an App Store link. JSON and CSV file export is free for any period. Allowing a refused write enables only the requested Health types. The app shows which types each agent may write and explains permission or format problems when a write cannot be applied.
0.1.2
Agent only; there was no App Store release of the iPhone app with this version.
Agent — 2026-11-08
Pairing can finish in the background after you pick the code on your iPhone. Pairing and receiving handle temporary Relay errors and busy local files more reliably.
0.1.1
iPhone app — 2026-11-06
Apple Health sync is more stable. Settings now includes Diagnostics, and your agent can ask for access to more Health types. You review those requests on your iPhone. Repeated deletion uploads are avoided, and command confirmations survive agent updates.
Agent — 2026-11-06
The agent keeps received data as daily JSON files for 30 days and offers signed instructions through MCP or the CLI. It can send Health access requests and receive diagnostics after you approve them on your iPhone.