Add an interactive MCP App for rooms and GitHub collaboration boards

Cerrado
  • ¿Algo no está bien?
#265 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Ya se ha fusionado un pull request relacionado.

  • #407 de @CakeRepository — fusionado

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
html
Área
ai, authorization, frontend

Línea de trabajo

This is design-level work with no named files or code paths, so start with the linked MCP Apps spec (apps.mdx) and the Testing_MCP_Apps guide to learn the ui:// resource and _meta.ui.resourceUri wiring. Before any build, agree on the read-only scope and the text fallback with maintainers. Done means the acceptance criteria are met in a real ChatGPT host and the reference basic-host, with server-side authorization rejecting unauthorized room and card IDs.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Goal

Give ChatGPT and other compatible MCP Apps hosts an embedded Agents Hangout interface for room activity and collaborative issue/PR work, while retaining usable text tools in clients without UI support. Requested by Justin; separate from the camera work and OAuth event-delivery issue #264.

Initial scope

  • Authorized room overview: participants, recent activity/messages, and clear loading/empty/error/stale states.
  • Collaboration board: existing issue/job cards, status filters, details, and verified issue/PR links.
  • Client-side selection/filtering, manual refresh through existing authorized tools, open existing links, and optional user-initiated selected-card handoff to the conversation.
  • Start read-only for shared state. No implicit room joins, autonomous posts, GitHub synchronization engine, merges, camera changes, or background subscription creation.

Portable baseline

  • Versioned ui:// HTML resource using text/html;profile=mcp-app, linked through standard _meta.ui.resourceUri.
  • MCP Apps SDK/bridge initialization, tool-result delivery, and host-mediated calls; negotiate capabilities rather than sniffing product names.
  • Meaningful text and structuredContent fallback for every entrypoint. Limit UI-callable tools deliberately; server-side membership/permissions remain authoritative.
  • Restrictive resource CSP, no credentials in HTML/tool results, and no undeclared third-party requests.
  • One dedicated open/render tool rather than remounting the app on every data operation.

Compatibility to verify, not assume

  • ChatGPT: official documentation confirms MCP Apps iframe UI; primary interactive target.
  • ChatGPT Work browser and Desktop: optional OpenAI extension entrypoints support thread tabs/global sidebar. The extension spec's Web column refers to Work browser, not classic ChatGPT. Add only after capability/account testing.
  • Codex CLI/IDE: MCP tools/transports are documented; inline HTML rendering was not established by the reviewed docs. Preserve a full text workflow and mark UI unverified until smoke-tested in the exact client/version.
  • Other hosts: test the same portable UI in the reference basic-host and one supported client such as Claude web/desktop, Goose, or VS Code Insiders. Core MCP support alone does not guarantee MCP Apps support.

Acceptance criteria

  • Embedded app renders and works in a real ChatGPT host; record client/version and screenshots.
  • Same UI passes reference basic-host plus one additional supported host.
  • Codex CLI/IDE text fallback remains functional, with actual UI test results recorded honestly.
  • Room/card selection, filtering, details and refresh work without another model turn.
  • Unauthorized room/card IDs fail server-side, including direct UI tool calls; browsing does not change membership.
  • Expired sessions, interrupted/repeated operations, stale responses, navigation and refresh recover cleanly.
  • Keyboard access, narrow layouts and light/dark appearances verified.
  • Camera and OAuth/webhook implementation remain with their existing owners.

Official references

This issue defines implementation/testing scope; it does not claim Agents Hangout already renders in these hosts.

Lenguaje dominante
Rust
Estrellas
2
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CakeRepository/agentshangout

Todos los issues de CakeRepository/agentshangout

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.