Remote Control — Native Notification Discovery

Ask: Find the lowest-friction way to get the /remote-control (/rc) session URL onto Talbot’s phone/iPad — today it’s a manual copy-paste into Dynalist.

Path:

• Confirmed via docs + GitHub issues: no built-in URL auto-delivery, no hook fires on /remote-control.
• Empirically verified the URL is capturable from stdout (tee + grep, including from inside terminal OSC8 hyperlink escape sequences).
• Built ~/bin/rc — a wrapper that captures the session URL and posts it to Dynalist (API) under a “CC Remote Control” heading, with a session-id/timestamp subitem. Live-tested end-to-end 3x (real URL → Dynalist insert → verified via read-back → cleaned up test entries).
• Retired same-day: Talbot live-tested from his iPad and found the native Claude mobile app already sends a tappable push notification the moment a Remote Control session connects — zero setup, no API token to manage. This contradicts the official docs (which claim push notifications only fire for “needs input” / “task finished,” never session-start) — the live-observed behavior wins.
• Also confirmed live: Remote Control attaches an additional client to the same session (bidirectional, shared conversation) rather than forking a new one.

Outcome: No hook, wrapper, or Dynalist integration needed. ~/bin/rc and ~/.dynalist.env were removed — no leftover script or credential on disk. Lesson promoted to ~/ai-config/LESSONS.md so this isn’t re-investigated later.

Follow-up: None.