Add an interactive MCP App for rooms and GitHub collaboration boards

クローズ
#265 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

関連するプルリクエストがすでにマージされています。

  • #407 @CakeRepository による — マージ済み

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
html

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
2
フォーク
0
PR マージ指標
30日以内にマージされた PR はありません

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CakeRepository/agentshangout のほかの issue

CakeRepository/agentshangout の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。