You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(serve-app): bind the host's own opening call instead of re-posting a large tool result (#562) (#565)
* fix(serve-app): bind the host's own opening call instead of re-posting a large tool result (#562)
The serve-app page posted the seeded tool result back to
POST /api/mcp/sessions/<id>/apps, so any opening result past the shared
64 KiB request-body bound (AB8010) dropped the App to the fallback panel —
cargo-hauler's dashboard on a busy machine, for one. The host already made
that call: McpAppRoutes gains an optional openingCall lookup, serve-app
supplies its selection, and the page binds by tool name alone. A request
that carries input and result (the Workbench) is unchanged; one that
carries only one of them, names another tool, or another session is still
AB8021.
* chore(changeset): reference the PR number
* fix(serve-app): one scrollbar, not three — block-size the host, sandbox, and surface-proxy iframes
An inline iframe at height:100% inside a 100%-tall body overflows by its
line-box descender, so the serve-app host page, the MCP App sandbox document,
and the Runtime App surface proxy each grew a scrollbar around the App's own.
Size the iframes as blocks and clip the framing documents' overflow.
* test(e2e): assert the sandbox proxy owns no scrollbar; tighten the changeset summary
Fix `agent-bundle serve-app` (and `serveApp`) showing the "ordinary tool result" fallback with `AB8010: Request body exceeds 64 KiB` instead of the App when the opening tool's result is large, and give a served App one scrollbar instead of three nested ones (the host page, the MCP App sandbox document, and the Runtime App surface proxy no longer scroll around it). (#565)
0 commit comments