{"version":"2.1.260","anchor":"bridge-environment-registration-can-now-include-a-host-profi","canonical_anchor":"bridge-environment-registration-can-now-include-a-host-profi","heading":"Bridge environment registration can now include a host profile","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/bridge-environment-registration-can-now-include-a-host-profi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Bridge environment registration can now include a host profile\n\nRemote environment registration can now include a host's tool and MCP server profile.\n\nThe `bridge_environment_register` API call used when registering a remote\/worker environment can now include a `host` field carrying host tools and the MCP server list, alongside the existing machine, directory, and branch metadata. The debug log now reports tool\/MCP counts for that host profile instead of dumping the full object.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}