{"version":"2.1.260","anchor":"runtime-controllable-browser-tool-exposed-to-published-artif","canonical_anchor":"runtime-controllable-browser-tool-exposed-to-published-artif","heading":"Runtime-controllable browser tool exposed to published Artifacts via a built-in host server","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/runtime-controllable-browser-tool-exposed-to-published-artif","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Runtime-controllable browser tool exposed to published Artifacts via a built-in host server\n\nPublished artifacts can now declare Claude's own browser tools as a host MCP server.\n\nThe Artifact tool's prompt text for host MCP servers now documents a built-in exception, `host:claude_browser`, which lets a published Artifact declare the Claude desktop app's own browser tools \u2014 `read_page`, `get_page_text`, `find`, `preview_start`, `navigate`, `computer`, and `form_input` \u2014 as a host server. Previously only user-configured local MCP servers could be declared this way.\n\n- Area: Artifacts\n- Names: `host:claude_browser`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5"}