Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Design] Redesign Planner tool activity

オープン
  • 何か問題がありますか？
#162 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

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

調査の方向性

Start with the Planner transcript tool activity in apps/web, the existing Chat.Activity summary and disclosure model, and /design-audit#surfaces. Compare AI Elements Tool and related progress components, then produce the required audit specimens and reference comparison before considering migration. Done includes approval, accessibility and reduced-motion evidence, screenshots for required states, and passing bun run types, bun run ci, bun test apps/web/src/chat, and bun run design-audit:test.

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

説明

Base branch: main
Branch: maggie/redesign-tool-activity
Depends on: None

Goal

Design a clear, compact tool-activity component for Planner messages using an established AI interface pattern.

Context From Planning

  • The current “2 tools · 600ms” disclosure and running state feel unfinished and hard to parse.
  • Evaluate AI Elements Tool first: https://elements.ai-sdk.dev/components/tool. Task and Chain of Thought may provide useful workflow-progress references.
  • External components are candidates for presentation only; Chopin's transcript event model remains the source of truth.

Current Behavior

The transcript summarizes running tools as a loader, tool name, and completed count. Finished runs collapse into count, failure count, and elapsed time, with a simple list of tool names/status/durations when expanded.

Desired Behavior

Provide a polished tool-activity row and disclosure that communicates running, completed, failed, and denied/refused activity clearly without dominating the transcript.

Acceptance Criteria

  • A library/reference evaluation documents what can be reused or adapted from AI Elements Tool and related progress components.
  • The audit shows zero/one/many tools, running, mixed completed/running, completed, failed, denied/refused, long names, and missing-duration states.
  • Summary and expanded rows have clear status icons, labels, elapsed time, and hierarchy.
  • Disclosure is keyboard accessible, preserves reduced-motion behavior, and returns a useful accessible name/state.
  • The implementation consumes existing Chat.Activity data and does not invent events or alter transcript persistence.
  • Maggie approves the audit specimen before production migration.

Verification Commands

  • bun run types
  • bun run ci
  • bun test apps/web/src/chat
  • bun run design-audit:test

Primary Surfaces

  • /design-audit#surfaces
  • Planner transcript tool activity in apps/web
  • Existing Chat.Activity summary and disclosure model

Expected PR Checks

  • Repo required checks

Report Requirements

  • Reference comparison and chosen pattern
  • Before/after screenshots for running, completed, and failed states
  • Accessibility and reduced-motion evidence
  • Any event-model gaps discovered, kept as follow-ups

Implementation Notes

  • Keep detailed tool names and status readable without exposing internal payloads or secrets.
  • Adapt visual patterns to Chopin tokens and component primitives.
  • Preserve current grouping of tool activity with the message that initiated it.

Stop Conditions

  • The desired UI requires protocol states Chopin does not currently receive.
  • A dependency would impose a conflicting transcript or AI SDK runtime model.
主要言語
TypeScript
スター
351
フォーク
20
平均マージ
14時間 38分
マージ済み PR（30日）
32

環境構築

このプロジェクトの環境構築ファイルはまだ確認していません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

githubnext/chopin のほかの issue

githubnext/chopin の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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