{"version":"2.1.119","anchor":"remote-control-server-configuration","canonical_anchor":"remote-control-server-configuration","heading":"Remote Control Server Configuration","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.119\/e\/remote-control-server-configuration","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.119","markdown":"### Remote Control Server Configuration\n\n**What**\n\nConfigure Remote Control bridge servers as persistent daemon workers, making sessions accessible from claude.ai.\n\n**Details**\n\n- Configured via `daemon.json` under the `remoteControl` key\n- Each server maps a local directory to a Remote Control endpoint\n- **Spawn mode**: `same-dir` (default) shares the directory, `worktree` gives each session its own git worktree\n- Configurable capacity (default 32 concurrent sessions), permission mode, sandbox mode, and session timeout\n- Sessions can be created on daemon start with `createSessionOnStart: true`\n- Manages the Remote Control bridge headlessly with automatic OAuth token management\n\n**Evidence**\n\nRemote control server configuration (search for `\"remote-control server\"`, `\"New Remote Control Server\"`, `\"spawnMode\"`)"}