GUI: Failure to open consecutive edited files under the << Files >> panel
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- frontend
Research direction
Reproduce the problem from the GUI Files panel using a task that edits multiple files, then trace the panel entry point and file-selection behavior. Compare opening the first file with opening a subsequent file and identify where the first preview remains active. Done means consecutive files open as separate adjacent panels without requiring the previous panel to be closed.
Written by the indexing model from the issue text.
Description
Summary
After the agent has edited multiple files, it display a table listing those files with the added/removed line counts; while we can click on those items, only the first on get to open under the Files panel, trying to open subsequent files failure, with the first opened persisted under the panel; it blip for a fraction of second though
Expected Behavior
Opening more files should preview them inside multiple adjacents panels -- with each file name as panel identifier
Actual Behavior
We always need to close the first file panel to to then open a new different one
Steps to reproduce the issue
- Execute a work that would edit a dozen of files
- Once the work is done, the agent should display a list of edited files, click on the first one; then clik another one
- the preview panel will blip for a second, then persist the first opened file
Command Code Version
0.1.40
Operating System
Windows
Terminal/IDE
No response
Shell
No response
Session file (optional)
No response
Fix prompt (optional)
No response
Additional context
No response
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 357
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from CommandCodeAI/command-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#933 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#855 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CommandCodeAI/command-code#841 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#655 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#608 ·
All issues in CommandCodeAI/command-code
Similar issues
-
agent-reported area/browser bug good first issue hacktoberfest help wanted P1
Difficulty 2/5 Half a day Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
full-stack
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kir-dev/pek-infinity#107 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
accessibility area:ai-suggestions bug good first issue P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
uttrflow/uttrflow-swift#1893 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day