Enterprise Best Practices & FAQ
Deploying remote control in an organization requires careful planning around compliance and managed settings.
Managed Settings
Administrators can use managed-settings.json to enforce policies:
permissions.disableBypassPermissionsMode: Disable--dangerously-skip-permissions.allowedMcpServers: Whitelist only approved plugins (like Telegram).forceRemoteSettingsRefresh: Fail-closed if the device is offline.
Troubleshooting Checklist
| Issue | Cause | Solution |
|---|---|---|
/remote-control is missing |
Unsupported provider (Bedrock/Vertex) | Use direct Anthropic OAuth. |
| Always allow rules lost | Worker restart bug in old versions | Upgrade to ≥ v2.1.118. |
| Telegram bot not responding | Missing --channels flag |
Restart with channel flag. |
| Pair code rejected | Pairing mode not enabled | /telegram:access policy pairing. |
Final FAQ
Q: Can I use both Remote Control and Telegram? A: Yes, they don't conflict. Many use Remote Control for deep work and Telegram for quick updates.
Q: Does it work on Windows/WSL? A: Yes. v2.1.119 added WSL inheritance for Windows managed settings.
Q: Is data safe? A: Remote Control transcripts stay in Anthropic cloud. Telegram messages stay on Telegram servers. Neither is 100% self-hosted.