Approval on the Mac
The Mac shows the requesting device name and asks you to allow or reject it before remote control begins.
Planned iPhone remote
A separate TeleNotch iPhone companion is planned for hands-off playback. The current pre-release builds use Mac approval, require encryption, and receive control commands without sending the script to the remote. The companion is not publicly available yet.
macOS 14+ · Apple silicon + Intel · No account
The remote is designed around an explicit approval step. Current pre-release builds accept one approved peer, surface connection errors, and keep the control path separate from the script library.
The Mac shows the requesting device name and asks you to allow or reject it before remote control begins.
Both targets require an encrypted Multipeer Connectivity session instead of accepting an unencrypted fallback.
TeleNotch rejects additional invitations while an approved phone is connected to the current session.
The companion sends play, pause, speed, reset, and scroll-back commands. It does not receive the current script text.
Step by step
Once released, both devices will need local-network permission and nearby connectivity. The iPhone companion will be installed separately from the direct Mac download.
Open TeleNotch Settings, go to Behavior, and turn on Remote Control so the Mac begins advertising the local session.
Allow Local Network access when requested. The companion will look for a nearby TeleNotch Mac and send one invitation.
Check the iPhone name shown in the Mac alert. Choose Allow only for a device you recognize.
The iPhone will show the Mac name after the encrypted session connects. If approval is declined or times out, use Try Again.
Verify play and pause, speed changes, reset, and scroll back while watching the Mac prompter respond.
The Mac app is planned as a signed and notarized website download. The iPhone companion is not bundled inside the Mac DMG and is expected to use the App Store as its separate installation path. This page will link to it only after the listing is publicly available.
Direct answers
No. The current pre-release protocol sends command names from the iPhone to the Mac. Script text remains in the Mac app.
No. The Mac shows an approval prompt with the requesting device name and accepts one user-approved peer for the session.
The pre-release companion shows a connection error and a Try Again action. The invitation allows time for the Mac approval step.
No. The planned companion will have its own App Store availability and installation step.
Keep exploring
The public release will be Developer ID signed and Apple notarized before it appears here.