CommandCodeAI / CommandCodeAI/command-code
bug: In Plan review cannot paste text when commenting
Open
@vipulgupta2048 is already working on this.
Since Sep 18, 2026.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.