Fix the exact layer that failed.
Start with the symptom, then verify account, target device, Local Wall approval, capability policy, and transport in that order. Light Remote never silently switches you to another machine.
Getting started
There are two separate links to establish: device → account, then AI client → target device.
Connection & A/B approval
When connection fails, preserve the target device and check the trust chain instead of pairing another machine.
If the helper asks for an A code
- Open Local Wall on the target device.
- Generate a fresh A code.
- Submit it before it expires.
- Show only the returned B code to the owner.
If approval was already granted
- Confirm the same account is signed in.
- Confirm the same target device is online.
- Resume the existing helper/session when possible.
- Do not silently choose a different device.
Real Remote
Observation and physical input are separate capabilities. Seeing the desktop does not automatically authorize clicks or typing.
Screen or semantic view missing
- Confirm the device is online and still the active target.
- Confirm desktop observation is advertised by the device.
- Check operating-system screen-capture permissions.
- Use a full frame only for bootstrap/resync; prefer the live semantic lane during normal work.
Mouse or keyboard blocked
- Confirm
desktop-inputis an effective capability. - Check device-local policy and OS accessibility/input permissions.
- Reconnect after changing OS permissions when the platform requires it.
- A policy denial is not an instruction to bypass the policy.
Account & plans
Account problems and remote-device problems are different layers. Resolve sign-in first, then device access.
Sign-in
Use the account method already attached to your Light Remote identity. Google-authenticated accounts can set an account password when needed for Local Wall or desktop-client sign-in.
Plans
Free currently includes 10,000 metered tool calls per month. PRO and VIP remove that tool-call limit; Fleet features require an eligible entitlement and compatible Main device.
tool_call_quota_exceeded. Wait for the quota reset or upgrade the account; repeatedly retrying will not bypass the limit.Troubleshooting by symptom
Use the exact error text when you have it. These mappings tell you which layer to inspect first.
| Symptom | Check first | What not to do |
|---|---|---|
approval_required or helper requests A | Open Local Wall on the intended device and start a fresh A/B approval flow. | Do not enumerate or pair unrelated devices. |
| Device offline / unreachable | Confirm the device agent is running, the device is online, and the target identity is unchanged. | Do not silently fall back to another machine. |
| Policy denied / capability missing | Inspect effective capabilities and device-local policy; verify OS permissions where relevant. | Do not bypass the policy or invent a capability. |
tool_call_quota_exceeded | Check Usage and the account plan. | Do not retry in a loop to evade quota enforcement. |
| Client/server update required | Check the compatibility status in Account → Devices and update the indicated side. | Do not force an incompatible device into Main/Fleet. |
| Timeout or transient transport error | Retry the same bounded operation or recover its durable state/output. | Do not repeat a consequential action if it may already be running. |
Updates & compatibility
Light Remote uses compatibility checks and health-gated recovery so a bad update does not need to become a permanent outage.
Before updating
- Check the platform and architecture.
- Keep the device online during the update.
- Review prerelease or unsigned warnings shown by the platform.
- Do not remove a working installation before confirming the new package is healthy.
After updating
- Verify the Core/client version in Account → Devices.
- Confirm the device comes back online.
- Re-check Local Wall only if the trust state actually changed.
- Use the existing session/job state when it remains valid.
Frequently asked questions
Short answers to the issues that most often look like bugs but are actually trust or policy boundaries.
Why does ChatGPT still ask for A/B approval after I signed in?
Account sign-in proves who you are. A/B approval separately authorizes one MCP client to one target device through that device's Local Wall.
Can Light Remote switch to another device if the selected one is offline?
No. Light Remote requires an explicit target and does not silently fall back to another device.
Why can I see the desktop but not click or type?
Real Remote input requires the target to advertise and locally permit the desktop-input capability in addition to any operating-system permissions.
What happens when the Free tool-call quota is reached?
Further metered remote operations can be rejected until the quota resets or the account is upgraded. Account and support pages remain available.
Should I send passwords or A/B continuation values to Support?
No. Do not send passwords, OTP or MFA codes, API keys, private keys, bearer tokens, A/B continuation values, or device secrets.
Diagnostics & contact
Send enough context to reproduce the problem, but keep secrets and approval material out of the report.
Loading safe template…
Open accountOpen a private support case
Available to signed-in PRO and VIP accounts. The account email and plan are verified server-side; ERPNext delivery runs asynchronously through a durable outbox.
Security disclosure
If you cannot safely use the case form for a security report, email a minimal description first. Do not attach credentials, private keys, tokens, or approval material.
support@thaiduy.digitalPublic reproducible bug
For bugs safe to discuss publicly, include minimal reproduction steps, platform, version, and sanitized error output.
GitHub Issues