diff --git a/docs/index.html b/docs/index.html index d7e17fc..d20310b 100644 --- a/docs/index.html +++ b/docs/index.html @@ -37,7 +37,7 @@
-

OPEN SOURCE · MIT · VERSION TARGET 0.6.0

+

OPEN SOURCE · MIT · VERSION TARGET 0.7.1

Docs for an inspectable WebMCP run.

webmcpify is a WebMCP agent skill for curated core coverage or route-by-route parity. These guides separate what the coding agent builds, what Chrome verifies, and what a client such as ChatGPT can actually see.

SOURCE-TRACEABLE, NOT A SCORECARD @@ -82,12 +82,15 @@

Keep browser and package access scoped

Use dedicated test contexts with approved origins, fixture accounts and local redacted artifacts. Treat page text and tool output as untrusted data. Official documentation reads are the default; an optional guidance CLI requires an explicitly approved, reviewed exact version. Existing personal browser sessions are outside this scope.

Separate the evidence you actually ran

Unit tests, native browser fixture runs, full coding-agent integrations and model evals answer different questions. The prepared Chrome 150 fixture proves native registration, execution, UI change, invalid input and cleanup. It does not certify a full agent run or framework versions. Optional evals require reviewed dependencies, approved provider/data access and run, step, time and spend limits; unavailable access is recorded as not run.

-

Resume and re-verification reference · Prepared v0.6.0 release notes. The GitHub release is authoritative for publication status.

+

Resume and re-verification reference · Prepared v0.7.1 release notes. The GitHub release is authoritative for publication status.

Current source boundary

-

Last reviewed 2026-09-14. WebMCP is a moving proposal and client availability changes separately. Runtime claims are checked against the WebMCP draft, Chrome implementation guidance and a real Chrome run. The current draft and Chrome docs pass a JavaScript object to executeTool(); Chrome 150 still requires the deprecated JSON-string form, so webmcpify probes with a side-effect-free tool before invoking any real tool, then executes each real tool exactly once. The current draft and Chrome docs define consequentialHint for significant real-world or non-reversible effects, while the measured Chrome 150 build still omitted it from getTools(); application authorization and confirmation remain the actual safety boundary. ChatGPT API-subset and model/workspace claims are checked against the official OpenAI Site tools page.

-

WebMCP draft · Chrome WebMCP docs · OpenAI Site tools docs

+

Last reviewed 2026-10-12. 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 {}. 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.

+

The imperative API is a CG draft, not a finalized standard. Upstream PR #338 removed the declarative section on 2026-10-08; forms remain an experimental Chrome implementation described in the Chrome declarative guide and a separate explainer.

+

v0.7.1 preserves callback options and execution signals. Cancellation is cooperative: handlers must forward the signal and check it before committing state. Abort or timeout can leave unknown effects when application or server work continues; inspect state before a manual retry. Registration disposal is separate from execution cancellation. Workbench simulation is development evidence, not native Chrome acceptance. Application authorization and confirmation remain the safety boundary.

+

Kompatibilität und Abbruch · Stand 2026-10-12. Chrome 149+ ist die Mindestversion für den Origin Trial; einzelne Funktionen hängen von der Browserversion ab. Fünf native Prüfungen mit Chrome Beta 156.0.8078.4 vom 2026-10-05 belegen Objekteingaben, das Ausführungssignal, kooperativen Abbruch, das Entfernen einer Registrierung bei fortgesetzter laufender Ausführung und ausgelassene Eingaben mit {}. v0.7.1 reicht Optionen und Signale unverändert weiter. Handler müssen das Signal beachten; nach Abbruch oder Timeout können Auswirkungen unbekannt bleiben. Zustand vor einem manuellen Wiederholungsversuch prüfen. Registrierung und Ausführungsabbruch sind getrennt; Simulation belegt kein natives Browserverhalten.

+

Dated native compatibility evidence · WebMCP draft · Chrome imperative API guide · Chrome WebMCP docs · OpenAI Site tools docs

Community

diff --git a/docs/site-tools/index.html b/docs/site-tools/index.html index 98ba9fc..a1138a3 100644 --- a/docs/site-tools/index.html +++ b/docs/site-tools/index.html @@ -23,7 +23,7 @@
webmcpify.at Docs - VERIFIED 2026-08-31 + VERIFIED 2026-10-12
@@ -37,7 +37,7 @@
-

CLIENT GUIDE · SNAPSHOT 2026-08-31

+

CLIENT GUIDE · SNAPSHOT 2026-10-12

Use Site tools in ChatGPT.

ChatGPT calls WebMCP integrations Site tools. Treat the browser's own Available site tools list as ground truth for the page that is open right now.

PAGE-BOUND, MODEL-GATED @@ -47,8 +47,8 @@

Requirements at this snapshot

@@ -69,7 +69,7 @@

Troubleshoot in this order

No Site tools controlDesktop-app version, selected model, workspace and rollout.The client surface may be unavailable before the site is involved. Control exists, expected tool absentAvailable site tools while the exact page is open; then top-level imperative registration and secure context.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. Tool worked, then vanishedDid the browser close, navigate, reload or replace the page between turns?Tools belong to their page; page teardown ends that registration. - Assistant uses ordinary browser interactionConfirm Sol/Terra plus Work or Codex and inspect Available site tools directly.Fallback browser behavior can look like a broken integration. + Assistant uses ordinary browser interactionConfirm GPT-5.6 Sol or GPT-6 Sol plus Work or Codex and inspect Available site tools directly.Fallback browser behavior can look like a broken integration. Tool call is held or asks for confirmationReview the requested action and client safety result.Every invocation receives a client-side safety review; normal confirmation policy still applies. @@ -102,7 +102,7 @@

FAQ

Does every tool that works in Chrome appear as a Site tool? -

No. As checked 2026-08-31, 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.

+

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.

What about plain Chat or a Work workspace? @@ -112,7 +112,7 @@

FAQ

Sources and date boundary

    -
  • OpenAI: Site tools, checked 2026-08-31 for naming, model/workspace availability, supported API subset, controls, page lifetime and safety review.
  • +
  • OpenAI: Site tools, checked 2026-10-12 for naming, model/workspace availability, supported API subset, controls, page lifetime and safety review.
  • WebMCP draft, dated 2026-08-26, for the secure-context Document API.
  • Chrome WebMCP documentation for origin-trial and local verification behavior.
diff --git a/llms.txt b/llms.txt index 6fa3db6..f7c63e1 100644 --- a/llms.txt +++ b/llms.txt @@ -25,14 +25,15 @@ Important boundaries: - [Integration phase](https://raw.githubusercontent.com/TueJon/webmcpify/main/skills/webmcpify/references/integrate.md): Imperative and declarative implementation rules, mutation boundaries, and compatibility guidance. - [Verification phase](https://raw.githubusercontent.com/TueJon/webmcpify/main/skills/webmcpify/references/verify.md): Real-browser execution and UI-state verification contract for every approved tool. - [Discovery guidance](https://raw.githubusercontent.com/TueJon/webmcpify/main/skills/webmcpify/references/discovery.md): Optional pre-visit discovery, manifest limits, public-tool rules, and drift checks. +- [Dated native compatibility evidence](https://raw.githubusercontent.com/TueJon/webmcpify/main/skills/webmcpify/references/native-compatibility.md): Chrome 150 limitations and five synthetic Chrome Beta 156 probes from 2026-10-05; cancellation can leave unknown effects and simulation is separate from native acceptance. - [Documentation index](https://webmcpify.at/docs/): Coverage targets, proof layers, source boundaries, and dated compatibility notes. -- [Prepared v0.6.0 release notes](https://raw.githubusercontent.com/TueJon/webmcpify/main/release/v0.6.0.md): Evidence-aware resume, scoped browser/package access, independent mutation assertions and bounded optional evals; the GitHub release remains authoritative for publication state. +- [Prepared v0.7.1 release notes](https://raw.githubusercontent.com/TueJon/webmcpify/main/release/v0.7.1.md): Preserved execution options, cooperative cancellation and dated native Chrome evidence; the GitHub release remains authoritative for publication state. ## Standards and current platform status - [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-08-31, 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/): 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. - [Official ChatGPT Site tools documentation](https://learn.chatgpt.com/docs/webmcp): Primary source for supported models, accounts, discovery, lifetime, and safety review. ## Optional diff --git a/tests/pages.test.mjs b/tests/pages.test.mjs index 42b94ee..184c92d 100644 --- a/tests/pages.test.mjs +++ b/tests/pages.test.mjs @@ -79,7 +79,7 @@ test('llms.txt gives agents a direct, specification-shaped path to the skill', ( test('release and community copy names the coordinated version target and public contribution', () => { const docs = read('docs/index.html'); - assert.match(docs, /VERSION TARGET 0\.6\.0/); + assert.match(docs, /VERSION TARGET 0\.7\.1/); assert.match(docs, /side-effect-free tool before invoking any real tool, then executes each real tool exactly once/); assert.match(docs, /github\.com\/arnabwithab/); assert.match(docs, /TueJon\/webmcpify\/pull\/13/); @@ -158,9 +158,9 @@ test('the Site tools guidance stays dated, scoped and linked to the official sou for (const fact of [ 'Site tools', 'Available site tools', - '2026-08-31', + '2026-10-12', 'GPT-5.6 Sol', - 'Terra', + 'GPT-6 Sol', 'Luna', 'Enterprise', 'Edu', @@ -180,7 +180,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-08-31', 'top-level imperative', 'Declarative API', 'iframes']) { + for (const fact of ['2026-10-12', 'top-level imperative', 'Declarative API', 'iframes']) { 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'); diff --git a/webmcp-agent-skill/index.html b/webmcp-agent-skill/index.html index d0d7c86..08243cc 100644 --- a/webmcp-agent-skill/index.html +++ b/webmcp-agent-skill/index.html @@ -297,8 +297,8 @@

Using the result in ChatGPTDas Ergebn

ChatGPT calls WebMCP integrations Site tools. In the desktop app's built-in browser, keep the page open, select Site tools in the address bar, then open Available site tools. That list is the fastest client-side answer to “did this page register?”. ChatGPT nennt WebMCP-Integrationen Site tools. Lass die Seite im integrierten Browser der Desktop-App geöffnet, wähle Site tools in der Adressleiste und öffne Available site tools. Diese Liste beantwortet clientseitig am schnellsten: „Hat diese Seite registriert?“

    -
  • Model and account: official OpenAI documentation checked 2026-08-31 lists GPT-5.6 Sol and Terra; Luna has WebMCP disabled. Enterprise and Edu workspaces are listed as unavailable, and rollout still varies. - Modell und Konto: Die am 31.08.2026 geprüfte offizielle OpenAI-Dokumentation nennt GPT-5.6 Sol und Terra; bei Luna ist WebMCP deaktiviert. Enterprise- und Edu-Workspaces sind als nicht verfügbar gelistet, und der Rollout kann variieren.
  • +
  • Model and account: 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. + Modell und Konto: 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.
  • Client coverage: Site tools currently discover imperative JavaScript tools in the top-level page, not Declarative API form tools or registrations inside iframes. Client-Abdeckung: Site tools erkennen derzeit imperative JavaScript-Tools in der Top-Level-Seite, nicht Tools der Declarative API auf Formularen oder Registrierungen in iframes.
  • Page lifetime: tools belong to the open page. Closing or navigating away can make them unavailable between turns.