{"version":"2.1.260","anchor":"remote-control-machine-profile-sharing-setting","canonical_anchor":"remote-control-machine-profile-sharing-setting","heading":"Remote Control machine-profile sharing setting","tier":"use","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/remote-control-machine-profile-sharing-setting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Remote Control machine-profile sharing setting\n\nA new setting controls how much machine info Remote Control shares when it registers a device.\n\nA new `remoteControl.shareHostProfile` setting controls what a Remote Control environment learns about the local machine when it registers. `off` reports nothing, `basic` reports OS\/architecture\/dev tools, and `full` also reports configured MCP server names (never the contents of a repo's `.mcp.json`). If left unset, the level falls back to remote rollout config. Managed settings, `--settings`, and user settings combine to the most restrictive value among them, while project and local settings can only lower the level further, never raise it.\n\n- Flag `tengu_bridge_host_profile`: Not enough to say (read for one account on one subscription tier against v2.1.260; this account: no value returned, anonymous baseline: no value returned, compiled default: no gate table built for this version) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Control\n- Names: `remoteControl.shareHostProfile`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}