CommandCodeAI / CommandCodeAI/command-code

bug: In Plan review cannot paste text when commenting

Abierto
#886 1 comentario 0 reacciones 1 asignado Ver en GitHub

@vipulgupta2048 ya está trabajando en esto.

Desde el 18/9/2026.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
4k
Forks
350
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

Summary
  • I requested a plan and began the review.
  • got to a place where I needed to comment and add a list of some topics
  • I had these from another place so I copied to clipboard
  • This was the list:
  - Agent Harnesses, Multi-Agent Systems & Orchestration — multi-agent
  - Agentic Coding, CLI Agents & Terminal Workflows — agentic-coding
  - AI-Native Products & Agent Platforms — ai-products
  - Design, Prototyping & Product UX — ai-design
  - Evaluation, Testing & Reliability — evaluation
  - Knowledge, Retrieval & Context Engineering — rag-patterns
  - Models, Open Source & Infrastructure — infrastructure
  - Team Workflows, Collaboration & Best Practices — ai-workflows
  • I commented "for the topics the json storage in db is fine but for UI include these topics: " and then I ctrl-v to paste. It was in clipboard because I just pasted it above
  • But, the text did not paste so my comment is incomplete
Expected Behavior

Paste to paste in the clipboard text into a comment so that review next round can consider the full comment

Actual Behavior

Did not paste

Steps to reproduce the issue

See above.

Command Code Version

1.0.56

Operating System

macOS

Terminal/IDE

No response

Shell

Ghostty

Session file (optional)

No response

Fix prompt (optional)

Plan a feature that creates a db table with topics as json. When in plan review add comment that the topic list for ui should ... and then past in a list of topics to see clipboard paste works. on plan review next cycle the topics listed should be included in next round.

Additional context

No response

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.