remove MCP App UI elements #113

Closed
opened 2026-07-20 19:02:54 +00:00 by coilysiren · 3 comments
Owner

not worth maintaining - MAYBE I will bring some map stuff back eventually - but for UI we remove the MCP App UI elements

not worth maintaining - MAYBE I will bring some map stuff back eventually - but for UI we remove the MCP App UI elements
Member

Director scope for a headless implementation: remove the MCP Apps iframe/widget layer completely while preserving the MCP tools themselves. Delete resource registrations for ui://eco/*, tool _meta.ui/widget payloads, template rendering, and now-dead Jinja templates/dependencies. Keep each tool’s markdown/text and structured JSON results, the browser SPA, and all /preview*.json endpoints intact. Update tests and the feature/docs inventory so they no longer claim inline MCP App cards. Validate the repo gates.

Director scope for a headless implementation: remove the MCP Apps iframe/widget layer completely while preserving the MCP tools themselves. Delete resource registrations for `ui://eco/*`, tool `_meta.ui`/widget payloads, template rendering, and now-dead Jinja templates/dependencies. Keep each tool’s markdown/text and structured JSON results, the browser SPA, and all `/preview*.json` endpoints intact. Update tests and the feature/docs inventory so they no longer claim inline MCP App cards. Validate the repo gates.
Member

WARDED_WORKFLOW: done

details

Removed MCP App resources, widget metadata, HTML templates, and Jinja dependency while retaining MCP text/JSON tools and preview routes. Tests and documentation now cover the data-only contract.

workflow: merge-remote-main; review summary: in-container review gate skipped intentionally pending brokered QA.

Felt: clean simplification once the resource and result contracts were traced.

Confidence: high. Surprises: remote main advanced during the run and was merged before landing. Follow-ups: none.

WARDED_WORKFLOW: done ✅ <details><summary>details</summary> Removed MCP App resources, widget metadata, HTML templates, and Jinja dependency while retaining MCP text/JSON tools and preview routes. Tests and documentation now cover the data-only contract. workflow: merge-remote-main; review summary: in-container review gate skipped intentionally pending brokered QA. Felt: clean simplification once the resource and result contracts were traced. Confidence: high. Surprises: remote main advanced during the run and was merged before landing. Follow-ups: none. </details>
Member

WARDED_WORKFLOW: reservation-released

release details

Run finished with WARDED_WORKFLOW: done ✅.

ward container reap released container engineer-codex-eco-app-113 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARDED_WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARDED_WORKFLOW: done ✅`. `ward container reap` released container `engineer-codex-eco-app-113` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/eco-app#113
No description provided.