Repository navigation
[FEATURE]: Managed pairing and remote access controls #59683
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Organizations deploying OpenCode through MDM need central control over pairing and the background service's internet tunnel.
I propose adding pairing and remote settings to the existing managed configuration. Policy changes would apply without restarting the server, preserve owner-password access, and take precedence over user configuration. This would use existing profiles and managed files, with no new UI.
This extends the managed settings and macOS preference support discussed in #6358 and #19158. The request is specifically for administrator control over pairing and tunnel access, rather than additional remote-control features.
I have a local prototype and regression tests, but have not opened a PR. Would maintainers approve this scope and configuration approach for an implementation PR? Application-level enforcement cannot prevent a local administrator from replacing OpenCode.
Activity
opencodejr commentedon Oct 27, 2026
Thanks for the detailed proposal and for checking first whether the scope fits.
To restate it: you'd like administrators to be able to set
pairingandremotein the managed configuration (managed files and macOS managed preferences). Those settings would control pairing and the background service's internet tunnel, override user configuration, apply without a server restart and leave owner-password access working.Today, remote access is only a per-user setting in the CLI's service configuration, and the managed configuration has no pairing or tunnel controls, so this would be a new capability. Maintainers will consider the scope and the configuration approach. Since you already have a prototype with regression tests, their answer here should tell you whether to open the PR.
Related issues: