Keep written guidance manageable during an authorized practice session. Remote Pad controls the desktop overlay from a mobile browser on the same trusted network. It does not speak answers aloud or mirror the desktop onto the phone.
Use only where assistance is explicitly permitted. Agree on screen capture and audio processing before a session, and follow the acceptable-use policy.
Use the same trusted Wi-Fi, or a computer on Ethernet that is reachable from the phone's Wi-Fi network. The beta requires private IPv4 connectivity. Guest-network isolation, firewalls or a VPN can prevent access. A phone using cellular data on a different network cannot use an internet relay through Remote Pad.
Open Settings and select Start Remote Pad. Scan the QR code with the phone camera and open the local page. Enrollment stays open for 10 minutes; already paired tabs can reconnect during the four-hour session. Stopping or restarting Remote Pad invalidates the old session.
Wait for Connected and control feedback. Up to four devices can pair, but one controls the desktop at a time. If another device has control, select Take control. Verify a small movement on the desktop before relying on the phone.
The transport is local HTTP and WebSocket without encryption. Keep the pairing link private and stop Remote Pad when finished. Remote Pad control is included in ClawPad subscription plans, with no separate add-on. AI actions still require the corresponding account access and use AI credits.
Control behavior checked against the current application source on October 13, 2026. This walkthrough is illustrative; it is not a recording or a claim of testing on a physical phone.
A quick horizontal swipe docks the overlay to the left or right half of the display. Tap the left or right column for the same placement, or tap the center column to center it. Docking can change the overlay size; it is different from a free-position drag.
These gestures request explicit hidden or visible states. Up shows the window; it does not center or enlarge it. Snap recognizes a swipe longer than 35 CSS pixels completed in under 450 milliseconds. A slower drag is not a swipe command. The labeled Hide Overlay and Show Overlay buttons avoid that timing requirement.
Move inside the Fine-Tune touch pad to shift the overlay without changing its size. This is separate from the Snap area. Watch the desktop and release when the overlay is positioned over the practice material you are authorized to capture.
The phone shows a size preview while two fingers move. Releasing a finger applies one bounded resize. It does not continuously resize the desktop during the pinch. Use the size buttons to adjust width or height. Repeat small adjustments while checking the desktop.
Analyze Screen requests desktop capture and analysis. The separate multi-screen controls collect up to five screens in reading order before analysis. Next Answer requests a deeper answer; it is not a button for paging through stored answer stages. These AI actions can consume credits.
Hide Overlay changes window visibility. It does not stop audio processing, erase an answer or disable the saved capture-exclusion setting. Restore with Show Overlay or the configured desktop Show or Hide Overlay shortcut. Confirm the actual window state if a command reports an error.
This sequence uses harmless existing content and window controls. It is a suggested test, not measured device evidence.
Pair the phone, tap the center Snap column and observe the desktop. Switch to Fine-Tune, drag a short distance, then pinch and release a finger. Record whether the desktop moved and resized as expected.
Use Hide Overlay, confirm the window disappears locally, then use Show Overlay and confirm it returns. Try the configured desktop shortcut too. Do not infer that hiding stopped Live Assist or that showing verified capture exclusion.
Briefly background the phone page, return to the paired tab, and wait for connection and control feedback. Confirm a new harmless movement. Record failure if it does not recover; no guaranteed reconnect time is claimed.
Before sharing, use the receiver-side capture verification method. Include phone-driven moves, resizes and reveals in that test. On macOS, a size or scale change can make capture application unconfirmed; use the desktop Re-apply control and test again. A phone acknowledgment is not evidence of what meeting participants receive.
Connection feedback describes the control link. It does not certify screen sharing or recording privacy.
Confirm both devices are on the same reachable network. The page attempts reconnects with increasing delays, capped at five seconds between retries. Use Reconnect to retry. This is retry timing, not a promise that recovery takes five seconds. Inputs made while disconnected are not queued for later control.
If the page says pairing was rejected or expired, start a new Remote Pad session in ClawPad and scan the new QR code. Closing the enrollment window does not by itself end an already paired tab's session. Restarting the session does invalidate its old credentials.
Check Show or Hide Overlay and other needed shortcuts before starting. If the phone fails during a share, stop sharing before troubleshooting visibility. Use the desktop to stop Live Assist when needed. Never treat an unavailable phone as an automatic hide action.
See Privacy for cloud processing and Setup Guide for desktop readiness.
Remote Pad is ClawPad’s beta phone controller. Open its local web page by scanning the desktop QR code. It sends controls to the desktop for moving, resizing, showing, hiding and analyzing an authorized practice question. The phone is not a second answer screen.
No. It runs in a mobile browser on the same trusted local network as ClawPad. Browser and network behavior still need testing on your devices. The beta uses a private IPv4 address and does not provide an internet relay for a phone on a different network.
Not yet. The beta is disabled by default and uses unencrypted local HTTP and WebSocket connections. Pair only on a network you trust. The phone receives control feedback, not a stream of your desktop screen. This does not mean AI processing is local; submitted questions use managed cloud AI.
No. Hide Overlay hides the desktop window. Show Overlay requests that it be shown again. These controls do not stop Live Assist, end the practice session, clear an answer or change the saved capture-exclusion preference. Stop audio processing using the desktop Live Assist controls.
No. In Snap, a quick upward swipe requests Show Overlay. A left or right swipe docks it to that half of the display. Tap the center column to center it. Use Fine-Tune to move or resize.
Controls are unavailable while disconnected. The page tries to reconnect using its session credential; Reconnect lets you retry. Reopen the paired tab on the same network. If the pairing is rejected, expired or stopped, start a fresh Remote Pad session on the desktop and scan its new QR code. Use the configured desktop shortcuts while the phone is unavailable.