The new Health Data interface
Preview guide · Updated 13 November 2026 (Hong Kong). These redesigned flows are in test builds. They are not a new App Store release. Use the released-app guide if your screens look different. A preview may disable purchases or cloud services; installing it does not unlock Pro.
Start with what you want to do
| Your goal | Where to go | What happens |
|---|---|---|
| Get a file for a spreadsheet, backup or Mac import | Export on iPhone | Choose format and date range, then save or share an exported copy. |
| Move an export from iPhone to Mac | Sync on iPhone; Wi-Fi Sync on Mac | Choose nearby transfer or a configured storage destination. |
| Let another tool read a saved Mac analysis | Local API Server on Mac | Select data, choose the tool, review access, then explicitly connect. |
| Share a smaller recent summary with an AI app | AI → Export to AI on iPhone | Create a 90-day JSON summary and manually share or attach it. |
Export: your data in a file
Choose the range and format for your task. Use XML for the Mac import workflow; use CSV or JSON when your destination supports it. A full export is different from the smaller AI summary. Large histories take longer: progress can pause while a category is being read. Keep the app open and follow its progress rather than starting another export.
Saving a file does not automatically upload it. Sharing it with a service or person gives that recipient a copy. See export instructions.
Wi-Fi Sync and cloud storage: two different routes
Wi-Fi Sync: iPhone export → same Wi-Fi → your Mac
Cloud storage: iPhone export → chosen storage service → your Mac
Wi-Fi Sync, step by step
- Connect iPhone and Mac to the same Wi-Fi network. Keep both apps open.
- Open Wi-Fi Sync on Mac and confirm the same-Wi-Fi check.
- Explicitly turn on receiving, then generate a pairing code on Mac.
- On iPhone, choose Direct to Mac and follow its connection instructions. Use the Mac address or discovery option shown in your build, then pair using the code.
- Start a transfer on iPhone and check that the export arrives on Mac. Pairing alone does not send all your data.
Use Back or Change to revise your choices. Stop receiving when you do not want nearby transfers. If a pairing code expires, generate a new one. Guest Wi-Fi or network isolation can prevent discovery even when network names match. Nearby transfer is not unattended automatic sync.
Cloud storage and background sync
On Mac, choose Use cloud storage instead to open the separate Cloud Sync route. iCloud uses your private CloudKit storage. Other destinations, including Google Drive, Dropbox and Nextcloud/WebDAV, use their own file or import flows; do not assume they refresh like iCloud. Configure the same destination on both devices and check the latest import status. Sync requires the relevant Pro entitlement. iOS decides when background work runs and may require an unlocked phone, so it is not a guaranteed schedule.
See destination setup. Home and Lock Screen widgets must be added through Apple’s widget editor; the app cannot silently place one. A Quick Sync shortcut needs a configured destination and the required entitlement. See widgets and shortcuts.
Local API Server: share selected Mac data with a tool
Saved Mac analysis → local read-only API → your chosen tool
- Choose data to share. Pick a saved analysis from History. This is the same History list, not a second library to maintain.
- Choose your tool. Select the supported connection route, such as OpenClaw or Local API.
- Review access. Check exactly which saved data the tool can read. Selecting data alone does not enable the server.
- Connect. Follow the route-specific instructions and explicitly enable access. Advanced API settings appear only for the Local API route.
Back and Change let you revise choices. Removing a selected History item makes that selection unavailable; choose another explicitly. History no longer needs a separate “Use with AI” button in this preview.
The server listens on 127.0.0.1:8765 and is read-only. Health-data endpoints require a token in the preview; only the two status routes are exempt. Do not expose the token or port publicly. See the API authentication guide, OpenClaw guide and MCP guide.
iPhone: Export to AI is not AI Chat
Export to AI prepares a JSON summary for ChatGPT, Claude, Gemini or Other (JSON). The tool choice does not connect an account or automatically attach a file to a new chat. Follow the handoff instructions, save/share the file, and attach it yourself in a compatible app.
The current preview’s shared summary covers the last 90 days: steps, sleep, workouts, heart rate, resting heart rate, heart-rate variability and blood glucose, when readable data is available. It is not every raw HealthKit record, and this summary does not include weight or mood. All four handoff choices use the same summary, not different model-specific datasets.
The 90-day range is this feature’s chosen scope, not a claim that an iPhone cannot process longer history. For a larger export, use the regular Export workflow and a destination that supports it.
AI Chat is not available in the current preview, even with Pro. The redesigned phone chat and paywall are being developed separately. Do not purchase Pro expecting this preview to answer questions. Existing Mac AI and existing Pro features are separate. No health data is sent simply by looking at the AI Chat preview.
Before sharing health data
- Local export and local models can keep processing on-device.
- Cloud sync sends a copy to the chosen storage service.
- Built-in cloud AI uses our service and provider infrastructure; other cloud-model routes send data to their configured provider.
- A local API or MCP connection is local, but the client can send its results onward.
- Review the categories and recipient before consenting. AI output is not a diagnosis or a replacement for medical advice.
Why does a workout warning appear after import?
A source workout may have timestamps spanning several days but a shorter recorded active duration. The preview uses exported active duration for totals and flags unusual timing for review rather than treating the full timestamp span as exercise. The original file is not rewritten. Reimport and reanalyze to apply parser changes to an older saved analysis.
Which build am I using?
Check the version and build shown in the app’s settings or About area. Preview notes describe test builds, not App Store availability. Released versions and release dates belong in the changelog; use the App Store to see which update is available for your device.