I found a small discrepancy between the spec and the examples.
Should the sandbox proxy method be ui/notifications/sandbox-ready or ui/notifications/sandbox-proxy-ready?
The draft spec states ui/notifications/sandbox-ready
#### Reserved Messages (Sandbox Proxy)
These messages are reserved for web-based hosts that implement the recommended double-iframe sandbox architecture:
`ui/notifications/sandbox-ready` (Sandbox Proxy → Host) - Sandbox proxy is ready
```typescript
{
jsonrpc: "2.0",
method: "ui/notifications/sandbox-ready",
params: {}
}
... but the examples use ui/notifications/sandbox-proxy-ready
|
const PROXY_READY_NOTIFICATION: McpUiSandboxProxyReadyNotification["method"] = |
|
"ui/notifications/sandbox-proxy-ready"; |
I found a small discrepancy between the spec and the examples.
Should the sandbox proxy method be
ui/notifications/sandbox-readyorui/notifications/sandbox-proxy-ready?The draft spec states
ui/notifications/sandbox-ready... but the examples use
ui/notifications/sandbox-proxy-readyext-apps/examples/basic-host/src/sandbox.ts
Lines 44 to 45 in 6f14cf3