Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ <h2>The three proof layers</h2>
<ol>
<li><b>Manifest proof:</b> the route map, policy fingerprint, approvals, examples and expected UI deltas are persisted in the target repository.</li>
<li><b>Chrome proof:</b> a dedicated headed profile enumerates and executes each tool against the recorded secure verification origin.</li>
<li><b>Client proof:</b> the exact client/account shows its supported subset of the page's registrations. In ChatGPT this surface is called <b>Site tools</b>; it currently discovers top-level imperative tools, not declarative forms or iframe registrations.</li>
<li><b>Client proof:</b> the exact client/account shows its supported tools. In ChatGPT this surface is called <b>Site tools</b>; official documentation checked 2026-11-09 describes JavaScript registration, HTML forms and secure same-origin or cross-origin iframes. Account/workspace policy and provider-origin permissions still apply.</li>
</ol>

<h2 id="maintenance">Maintain evidence after the first integration</h2>
Expand All @@ -85,6 +85,7 @@ <h3>Separate the evidence you actually ran</h3>
<p><a href="https://github.com/TueJon/webmcpify/blob/main/skills/webmcpify/references/reverify.md">Resume and re-verification reference</a> · <a href="https://github.com/TueJon/webmcpify/blob/main/release/v0.7.1.md">Prepared v0.7.1 release notes</a>. The GitHub release is authoritative for publication status.</p>

<h2>Current source boundary</h2>
<p><b>Additional read-only probe · 2026-11-09.</b> Headed Chrome 156.0.8078.47 returned object callbacks as JSON text, strings as unquoted text, and absent values as the string <code>undefined</code>. The draft's scalar serialization rules differ; preserve raw evidence and explicit result guards. This browser did not expose <code>outputSchema</code> metadata. Schema declaration is not automatic output validation, and simulation does not prove native support. A document-replacement probe timed out; no document-lifetime or WPT conformance pass is claimed.</p>
<div class="requirements">
<p><b>Last reviewed 2026-10-12.</b> Chrome 149+ is the WebMCP origin-trial minimum; support for individual features depends on the browser version and must be verified. The synthetic Chrome Beta 156.0.8078.4 run on 2026-10-05 passed five native probes: object input, callback execution signal, cooperative caller cancellation, registration removal preserving a started invocation, and omitted input defaulting to <code>{}</code>. Successful imperative results arrived as serialized JSON strings. This does not prove declarative navigation, debugging annotations or every Chrome version. Chrome 150 required legacy JSON-string input and lacked callback options and omitted-input support; webmcpify probes with a side-effect-free tool before invoking any real tool, then executes each real tool exactly once.</p>
<p>The imperative API is a CG draft, not a finalized standard. <a href="https://github.com/webmachinelearning/webmcp/pull/338" target="_blank" rel="noopener">Upstream PR #338</a> removed the declarative section on 2026-10-08; forms remain an experimental Chrome implementation described in the <a href="https://developer.chrome.com/docs/ai/webmcp/declarative-api" target="_blank" rel="noopener">Chrome declarative guide</a> and a separate explainer.</p>
Expand Down
24 changes: 12 additions & 12 deletions docs/site-tools/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Use ChatGPT Site tools with WebMCP — webmcpify docs</title>
<meta name="description" content="Dated setup and troubleshooting guide for ChatGPT Site tools: supported models, top-level imperative tool support, page lifetime and headed-Chrome verification.">
<meta name="description" content="Dated setup and troubleshooting guide for ChatGPT Site tools: account permissions, JavaScript and form tools, secure frames, page lifetime and Chrome verification.">
<link rel="canonical" href="https://webmcpify.at/docs/site-tools/">
<link rel="describedby" href="/llms.txt" type="text/markdown">
<link rel="webmcp" href="/.well-known/webmcp" type="application/json">
Expand All @@ -23,7 +23,7 @@
<div class="topbar-inner">
<a class="brand" href="/">webmcpify.at</a>
<a href="/docs/">Docs</a>
<span class="meta">VERIFIED 2026-10-12</span>
<span class="meta">DOCS CHECKED 2026-11-09</span>
</div>
</header>

Expand All @@ -37,7 +37,7 @@
</nav>

<main>
<p class="meta">CLIENT GUIDE · SNAPSHOT 2026-10-12</p>
<p class="meta">CLIENT GUIDE · SNAPSHOT 2026-11-09</p>
<h1>Use Site tools in ChatGPT.</h1>
<p class="lede">ChatGPT calls WebMCP integrations <b>Site tools</b>. Treat the browser's own Available site tools list as ground truth for the page that is open right now.</p>
<span class="stamp">PAGE-BOUND, MODEL-GATED</span>
Expand All @@ -47,9 +47,9 @@ <h2>Requirements at this snapshot</h2>
<ul>
<li><b>Website:</b> the page registers WebMCP from a secure context. Use HTTPS in production or a trustworthy loopback origin in development.</li>
<li><b>ChatGPT:</b> update the desktop app, then open the website in its built-in browser.</li>
<li><b>Model:</b> official OpenAI documentation checked 2026-10-12 lists GPT-5.6 Sol or GPT-6 Sol. GPT-5.6 Luna currently has WebMCP disabled.</li>
<li><b>Workspace:</b> the official page requires an administrator to allow Site tools through Enterprise workspace policy; Edu is unavailable, and availability can also depend on rollout.</li>
<li><b>Client API:</b> ChatGPT currently discovers imperative JavaScript tools in the top-level page. Declarative API form tools and tools registered inside iframes are not available as Site tools.</li>
<li><b>Model and access:</b> a supported model and access through your account or managed workspace's browser policy are required. The current official page does not list model names or a workspace exclusion matrix; verify access in the exact account.</li>
<li><b>Permissions:</b> browser settings and site permissions still apply. Check <b>Enable site tools</b> under <b>Settings → Browser → Permissions</b>.</li>
<li><b>Client API:</b> the official page documents JavaScript tools and HTML form tools in the top-level page and same-origin or cross-origin iframes. Each frame needs a secure context; access is checked for the tool provider's origin.</li>
</ul>
</div>

Expand All @@ -67,9 +67,9 @@ <h2>Troubleshoot in this order</h2>
<thead><tr><th>Symptom</th><th>Check</th><th>Meaning</th></tr></thead>
<tbody>
<tr><td>No Site tools control</td><td>Desktop-app version, selected model, workspace and rollout.</td><td>The client surface may be unavailable before the site is involved.</td></tr>
<tr><td>Control exists, expected tool absent</td><td>Available site tools while the exact page is open; then top-level imperative registration and secure context.</td><td>The page did not register it in the current document, registration failed, or it uses a declarative form or iframe that this client does not discover.</td></tr>
<tr><td>Control exists, expected tool absent</td><td>Available site tools while the exact page is open; registration or form metadata, frame secure context and provider-origin access.</td><td>Check document lifetime, registration errors and permissions rather than assuming iframe or form tools are unsupported.</td></tr>
<tr><td>Tool worked, then vanished</td><td>Did the browser close, navigate, reload or replace the page between turns?</td><td>Tools belong to their page; page teardown ends that registration.</td></tr>
<tr><td>Assistant uses ordinary browser interaction</td><td>Confirm GPT-5.6 Sol or GPT-6 Sol plus Work or Codex and inspect Available site tools directly.</td><td>Fallback browser behavior can look like a broken integration.</td></tr>
<tr><td>Assistant uses ordinary browser interaction</td><td>Confirm a supported model, account/workspace access and browser permissions; inspect Available site tools directly.</td><td>Fallback browser behavior can look like a broken integration.</td></tr>
<tr><td>Tool call is held or asks for confirmation</td><td>Review the requested action and client safety result.</td><td>Every invocation receives a client-side safety review; normal confirmation policy still applies.</td></tr>
</tbody>
</table>
Expand Down Expand Up @@ -102,7 +102,7 @@ <h2>FAQ</h2>
</details>
<details>
<summary>Does every tool that works in Chrome appear as a Site tool?</summary>
<p>No. As checked 2026-10-12, ChatGPT's built-in browser supports imperative tools registered in the top-level page, but not declarative form tools or registrations inside iframes. Regular browser interaction may still operate those forms.</p>
<p>No account-level compatibility promise follows from a Chrome test. The official guide checked 2026-11-09 documents JavaScript registration, HTML forms and secure same-origin or cross-origin iframes. Verify the actual account, provider-origin permissions and Available site tools list.</p>
</details>
<details>
<summary>What about plain Chat or a Work workspace?</summary>
Expand All @@ -112,11 +112,11 @@ <h2>FAQ</h2>

<h2>Sources and date boundary</h2>
<ul>
<li><a href="https://learn.chatgpt.com/docs/webmcp" target="_blank" rel="noopener">OpenAI: Site tools</a>, checked 2026-10-12 for naming, model/workspace availability, supported API subset, controls, page lifetime and safety review.</li>
<li><a href="https://webmachinelearning.github.io/webmcp/" target="_blank" rel="noopener">WebMCP draft</a>, dated 2026-08-26, for the secure-context Document API.</li>
<li><a href="https://learn.chatgpt.com/docs/webmcp" target="_blank" rel="noopener">OpenAI: Site tools</a>, checked 2026-11-09 for account/workspace policy, form/frame discovery, controls, page lifetime and safety review. This is a documentation check, not a live account test.</li>
<li><a href="https://webmachinelearning.github.io/webmcp/" target="_blank" rel="noopener">WebMCP draft</a>, dated 2026-11-02, for the secure-context Document API.</li>
<li><a href="https://developer.chrome.com/docs/ai/webmcp" target="_blank" rel="noopener">Chrome WebMCP documentation</a> for origin-trial and local verification behavior.</li>
</ul>
<p>Re-check these pages before copying model names or workspace claims into another public surface.</p>
<p>The official guide permits omitting <code>exposedTo</code> for agent discovery. This is distinct from in-page cross-origin discovery, which still requires embedder delegation, provider exposure and consumer opt-in. Re-check the primary sources before publishing availability claims.</p>
</main>
</div>

Expand Down
2 changes: 1 addition & 1 deletion llms.txt
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ Important boundaries:

- [WebMCP proposal](https://webmachinelearning.github.io/webmcp/): W3C Web Machine Learning Community Group draft for page-provided tools.
- [Chrome WebMCP documentation](https://developer.chrome.com/docs/ai/webmcp): Current Chrome origin-trial and implementation guidance.
- [Using Site tools in ChatGPT](https://webmcpify.at/docs/site-tools/): Dated setup and troubleshooting guide. As checked on 2026-10-12, ChatGPT discovers top-level imperative JavaScript tools, not Declarative API forms or registrations inside iframes; availability varies during rollout.
- [Using Site tools in ChatGPT](https://webmcpify.at/docs/site-tools/): Official documentation checked 2026-11-09 describes JavaScript registration, HTML forms and secure same-origin/cross-origin iframes; account/workspace policy and provider-origin permissions still apply. Documentation evidence is separate from account verification.
- [Official ChatGPT Site tools documentation](https://learn.chatgpt.com/docs/webmcp): Primary source for supported models, accounts, discovery, lifetime, and safety review.

## Optional
Expand Down
15 changes: 7 additions & 8 deletions tests/pages.test.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -158,20 +158,19 @@ test('the Site tools guidance stays dated, scoped and linked to the official sou
for (const fact of [
'Site tools',
'Available site tools',
'2026-10-12',
'GPT-5.6 Sol',
'GPT-6 Sol',
'Luna',
'Enterprise',
'Edu',
'2026-11-09',
'supported model',
'browser policy',
'safety review',
'Declarative API',
'HTML form',
'iframes',
'top-level page',
]) {
assert.ok(html.includes(fact), `${page} is missing dated Site tools fact: ${fact}`);
}
assert.ok(html.includes(official), `${page} must cite the official Site tools guide`);
assert.doesNotMatch(html, /GPT-5\.6 Sol|GPT-6 Sol|Edu is unavailable|not Declarative API/,
`${page} must not retain the superseded availability matrix`);
assert.match(
html,
/(?:keep (?:the )?(?:target )?page open|keep its browser tab open|page (?:stays|remains) open)/i,
Expand All @@ -180,7 +179,7 @@ test('the Site tools guidance stays dated, scoped and linked to the official sou
}

const machineSummary = normalize(read('llms.txt'));
for (const fact of ['2026-10-12', 'top-level imperative', 'Declarative API', 'iframes']) {
for (const fact of ['2026-11-09', 'HTML forms', 'cross-origin', 'provider-origin']) {
assert.ok(machineSummary.includes(fact), `llms.txt is missing Site tools boundary: ${fact}`);
}
assert.ok(machineSummary.includes(official), 'llms.txt must cite the official Site tools guide');
Expand Down
12 changes: 6 additions & 6 deletions webmcp-agent-skill/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -297,10 +297,10 @@ <h2><span lang="en">Using the result in ChatGPT</span><span lang="de">Das Ergebn
<p><span lang="en">ChatGPT calls WebMCP integrations <b>Site tools</b>. In the desktop app's built-in browser, keep the page open, select <b>Site tools</b> in the address bar, then open <b>Available site tools</b>. That list is the fastest client-side answer to “did this page register?”.</span>
<span lang="de">ChatGPT nennt WebMCP-Integrationen <b>Site tools</b>. Lass die Seite im integrierten Browser der Desktop-App geöffnet, wähle <b>Site tools</b> in der Adressleiste und öffne <b>Available site tools</b>. Diese Liste beantwortet clientseitig am schnellsten: „Hat diese Seite registriert?“</span></p>
<ul>
<li><span lang="en"><b>Model and account:</b> official OpenAI documentation checked 2026-10-12 lists GPT-5.6 Sol or GPT-6 Sol; Luna has WebMCP disabled. Enterprise requires an administrator to allow Site tools through workspace policy; Edu is unavailable, and rollout still varies.</span>
<span lang="de"><b>Modell und Konto:</b> Die am 12.10.2026 geprüfte offizielle OpenAI-Dokumentation nennt GPT-5.6 Sol oder GPT-6 Sol; bei Luna ist WebMCP deaktiviert. In Enterprise muss ein Administrator Site tools per Workspace-Richtlinie erlauben; Edu ist nicht verfügbar, und der Rollout kann variieren.</span></li>
<li><span lang="en"><b>Client coverage:</b> Site tools currently discover imperative JavaScript tools in the top-level page, not Declarative API form tools or registrations inside iframes.</span>
<span lang="de"><b>Client-Abdeckung:</b> Site tools erkennen derzeit imperative JavaScript-Tools in der Top-Level-Seite, nicht Tools der Declarative API auf Formularen oder Registrierungen in iframes.</span></li>
<li><span lang="en"><b>Model and account:</b> official documentation checked 2026-11-09 requires a supported model and access through your account or managed workspace's browser policy. It does not list model names or workspace exclusions; check the actual account and browser permissions.</span>
<span lang="de"><b>Modell und Konto:</b> Die am 09.11.2026 geprüfte offizielle Dokumentation verlangt ein unterstütztes Modell und Zugriff über das Konto oder die Browser-Richtlinie des verwalteten Workspace. Modellnamen und Workspace-Ausschlüsse werden nicht aufgelistet; prüfe das konkrete Konto und die Browser-Berechtigungen.</span></li>
<li><span lang="en"><b>Client coverage:</b> the guide documents JavaScript tools and HTML forms in the top-level page and same-origin or cross-origin iframes. Every frame needs a secure context; access is checked for the tool provider's origin.</span>
<span lang="de"><b>Client-Abdeckung:</b> Der Leitfaden beschreibt JavaScript-Tools und HTML-Formulare in der Hauptseite sowie gleich- und fremdoriginären iframes. Jeder Frame braucht einen sicheren Kontext; der Zugriff wird für die Herkunft des Tools geprüft.</span></li>
<li><span lang="en"><b>Page lifetime:</b> tools belong to the open page. Closing or navigating away can make them unavailable between turns.</span>
<span lang="de"><b>Seiten-Lebensdauer:</b> Tools gehören zur geöffneten Seite. Schließen oder Wegnavigieren kann sie zwischen Turns unverfügbar machen.</span></li>
<li><span lang="en"><b>Safety:</b> every invocation receives a client-side safety review; normal access and confirmation policies still apply.</span>
Expand All @@ -312,8 +312,8 @@ <h2>FAQ</h2>
<div class="faq">
<details>
<summary><span lang="en">Why do Site tools look missing in ChatGPT?</span><span lang="de">Warum wirken Site tools in ChatGPT verschwunden?</span></summary>
<p><span lang="en">Check the page's Available site tools list first, then top-level imperative registration, the current desktop-app version, supported model and workspace availability. Site tools die with the page, so keep its browser tab open. Chrome verification and ChatGPT account availability are separate checks.</span>
<span lang="de">Prüfe zuerst die Liste Available site tools der Seite, dann die imperative Registrierung auf der Top-Level-Seite, die aktuelle Desktop-App, ein unterstütztes Modell und die Workspace-Verfügbarkeit. Site tools sterben mit der Seite; lass ihren Browser-Tab offen. Chrome-Verifikation und ChatGPT-Kontoverfügbarkeit sind getrennte Prüfungen.</span></p>
<p><span lang="en">Check the page's Available site tools list first, then registration or form metadata, each frame's secure context, provider-origin permissions and account/workspace access. Site tools belong to the page, so keep its browser tab open. Chrome verification and ChatGPT account availability are separate checks.</span>
<span lang="de">Prüfe zuerst Available site tools, dann Registrierung oder Formular-Metadaten, den sicheren Kontext jedes Frames, Berechtigungen der Tool-Herkunft und Konto-/Workspace-Zugriff. Site tools gehören zur Seite; lass den Browser-Tab offen. Chrome-Verifikation und ChatGPT-Kontoverfügbarkeit sind getrennte Prüfungen.</span></p>
</details>
<details>
<summary><span lang="en">Which agents can run this skill?</span><span lang="de">Welche Agents können diesen Skill ausführen?</span></summary>
Expand Down
Loading