remove MCP App UI elements #113
Labels
No labels
burndown-2026-06
headless
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/eco-app#113
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
not worth maintaining - MAYBE I will bring some map stuff back eventually - but for UI we remove the MCP App UI elements
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*.jsonendpoints intact. Update tests and the feature/docs inventory so they no longer claim inline MCP App cards. Validate the repo gates.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: reservation-released
release details
Run finished with
WARDED_WORKFLOW: done ✅.ward container reapreleased containerengineer-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