github
The @ function cannot recognize files created while Copilot interactive mode is active.
Describe the bug
The @ function cannot recognize files created while Copilot interactive mode is active.
Affected version
0.0.343 Commit: 5847051
Steps to reproduce the behavior
- Type copilot
- Create new file
- Type @
Expected behavior
New file is not shown
Additional context
No response
Thank you for the report, I have noticed this as well and it bothers me. Will investigate.
I have been plagued by this, trying to create new screenshots to show copilot problems or examples of styling I want.
It would be really nice if the '@' command initially worked off the cached file list, but did an on-disk search (or just used fzf) in the background and updated the list when the results were available. Having to copy/paste new paths into a prompt just isn't ideal.
This would likely solve #448 and #594 as well.
I’m also affected by this issue.
When I type @ I expect the CLI to show the current, up-to-date directory and file index (including files created in my editor during the session).
If there are performance or other reasons preventing live indexing, please consider adding a slash command (for example /refresh or /reload-index) that explicitly refreshes the directory/file index.
Right now my only workaround is to exit and restart the CLI, which is disruptive.
