Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Widget: copy a completed assistant reply

Aberta
#477 2 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@piyusshhjangid já está trabalhando nisso.

Desde 30/10/2026.

  • #504 de @piyusshhjangid — aberto

Avaliação

Esta issue ainda não foi avaliada.

Descrição

hacktoberfest
What problem would this solve?

Visitors often need to reuse an answer outside the chat. Selecting a long rendered reply is awkward on phones and can be error-prone around formatted text and code blocks.

What would you like to happen?

Add a copy action to completed assistant replies. Copy the reply as readable plain text, preserving code block contents and line breaks without copying Markdown syntax. Keep the action out of the streaming state, make it keyboard accessible, and announce success or failure without disrupting the existing reply announcement.

Where to look
  • packages/widget/src/dom/messages.ts renders assistant messages and reply actions.
  • packages/widget/src/i18n.ts holds the widget’s accessible UI strings.
  • packages/widget/src/styles/widget.css contains message action styles.
  • packages/widget/tests/dom/messages.test.ts covers message rendering.
Acceptance criteria
  • A copy button is available for a completed assistant reply and is not shown while that reply is streaming.
  • Clipboard failures are handled without an uncaught error, including when the Clipboard API is unavailable.
  • The control has a localized accessible name, a visible focus indicator, and an accessible confirmation of the result.
  • Tests cover copying formatted content, streaming replies, and clipboard failure.
  • Add a widget changeset; keep the gzipped bundle within the configured size budget.
Contributing
  • I’d like to work on this myself
Linguagem predominante
TypeScript
Estrelas
13
Forks
7
Merge médio
3h 28min
PRs com merge (30d)
296

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codercops/chatcops

Todas as issues de codercops/chatcops

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.