Support

Cragen is local-first, so your training data is stored on the phone by default unless you enabled optional iOS account backup or approved selected data for connected coaching. If you signed in with Apple or email, open Settings → Account and try Restore Backup. If you only used local storage, an uninstall, device reset, or OS sandbox cleanup may have removed the data from that phone.

Make sure you're on the latest version from your device's app store. If it still crashes, write to support@cragen.app with your device model and OS version, and we'll dig in.

Open your OS settings and confirm Cragen has read permission for steps, sleep, and body weight. On iPhone: Settings → Privacy & Security → Health → Cragen. After granting, force-close and reopen Cragen. Android Health Connect support is still in testing.

Weight carry-forward uses your most recent matching set for that exercise. If you swapped exercises or never logged a first set, there's nothing to carry forward yet. Enter a target weight on the first set; subsequent sets and sessions will follow.

Confirm you are signed into the account that owns the training, then open Settings → Connected Coaches. You can review or decline a proposal there, retry a pending recovery, or disconnect that exact coach. A proposal never changes your current program or active workout automatically. A requested write can show as queued while it waits for your signed-in phone; queued is not applied. If the connection still looks wrong, disconnect it and email support@cragen.app. Never email us a pairing code, access token, refresh token, or proposal payload. For compatible agents, create a one-time connection prompt in Cragen, copy it to the agent, and use the official agent setup guide.

Apple may give Cragen your shared address or an Apple private-relay address. Adding a regular email is optional and creates an alternate sign-in for the same account. WorkOS uses the email, IP address, user agent, and device identifier only when you choose passwordless email; coach authorization instead uses an opaque ID and a non-contactable alias under coach-identity.cragen.app. Your real or relay sign-in email is not coach context. Read and proposal access uses connected-coaching-2026-09-01-v4; any new connection requesting a write uses connected-coaching-2026-09-05-v5. Prompt-only OAuth 2.0 Device Authorization is the primary path: you copy a one-time pairing invitation and approve the named agent in Cragen, with no website or credential required. WorkOS browser OAuth is a compatibility fallback. The permissions are Programs (programs.read), Training history (training.read), Profile (profile.read), Health summaries (health_summary.read), Current workout (live_training.read), Notes (notes.read), Program suggestions (programs.propose), Upcoming program workouts (programs.write), Personal exercises (exercises.create), Coach notes (coaching_notes.write), Training preferences (training_preferences.write), and Training reminders (reminders.write). Training only includes Programs, completed training, and program suggestions; it excludes Profile, Health summaries, Current workout, and Notes. Existing v4 grants keep their original seven permissions. Full coaching context remains those seven and does not include automatic writes; use Choose access to add a write. Program suggestions remain inactive until you approve them. Write requests wait for an authenticated device receipt, and Undo refuses to replace later edits or workout progress. Reminders require notification permission in system settings, support at most one enabled reminder per weekday and seven per connection, and must be set from 08:00 through 20:59 in their saved time zone. A pairing invitation expires after 30 minutes; its expired unclaimed, pending, denied, or cancelled record is deleted in the next bounded retention cleanup run, not instantly. Access tokens last 10 minutes and refresh tokens have a 30-day refresh lifetime. Approved connection and audit records follow their separate rules.