anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Opencode shows error when attaching a supported file after an unsupported one #996

New Issue
Closed
opened 2026-02-16 17:29:02 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:29:02 -05:00
Owner
Copy Link
Copy Source

Originally created by @cpalau on GitHub (Jul 30, 2025).

Originally assigned to: @adamdotdevin on GitHub.

Hi,

I am using GitHub Copilot with ChatGPT 4.1, which does not support PDF files but does support PNG images.

I have attached a video demonstrating the issue.

Steps to reproduce:

  1. First, attach a file type that the model does not support. It's correct that Opencode shows an error in this case.
  2. Next, attach a file type that the model supports, but an error is still displayed.
  3. Type /new.
  4. Try step 2 again, and this time it works fine.

Thanks,
Chris

Bug video:

https://www.loom.com/share/40472817dc1d437ebb3c5d2d59d591ab?sid=ffd5ccc7-1422-4cf4-b971-693c0912ffe9

Originally created by @cpalau on GitHub (Jul 30, 2025). Originally assigned to: @adamdotdevin on GitHub. Hi, I am using GitHub Copilot with ChatGPT 4.1, which does not support PDF files but does support PNG images. I have attached a video demonstrating the issue. Steps to reproduce: 1) First, attach a file type that the model does not support. It's correct that Opencode shows an error in this case. 2) Next, attach a file type that the model supports, but an error is still displayed. 3) Type /new. 4) Try step 2 again, and this time it works fine. Thanks, Chris Bug video: https://www.loom.com/share/40472817dc1d437ebb3c5d2d59d591ab?sid=ffd5ccc7-1422-4cf4-b971-693c0912ffe9
yindo closed this issue 2026-02-16 17:29:03 -05:00
yindo commented 2026-02-16 17:29:03 -05:00
Author
Owner
Copy Link
Copy Source

@adamdotdevin commented on GitHub (Aug 13, 2025):

we might consider removing messages from history altogether in these scenarios in the future, but in the meantime you can /undo to revert the last message and continue in your current session unaffected

@adamdotdevin commented on GitHub (Aug 13, 2025): we might consider removing messages from history altogether in these scenarios in the future, but in the meantime you can `/undo` to revert the last message and continue in your current session unaffected
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#996
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?