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

Shell commands are broken in message history and in opencode run #3510

New Issue
Closed
opened 2026-02-16 17:40:25 -05:00 by yindo · 4 comments
yindo commented 2026-02-16 17:40:25 -05:00
Owner
Copy Link
Copy Source

Originally created by @jdanbrown on GitHub (Dec 12, 2025).

Originally assigned to: @thdxr on GitHub.

Description

Bug 1: Shell commands are broken in message history

  • Send message !date → observe that ! changes the input box into "Shell" mode, and then date is input into the box and run as a shell command (correct)
  • Press up to recall your last message → date is recalled into the input box, but it isn't switched into Shell mode, so when you send it it's incorrectly sent as a message to the model instead of as a command to the shell

Bug 2: Shell commands are broken in opencode run

  • opencode run '!date' → sends the string !date to the model instead of running date as a shell command

Is the fancy switch into Shell mode actually worthwhile, or would it be better overall to remove that and just interpret messages that start with ! as shell commands? That would be one way to fix both of these issues by doing less, as well as any potential other issues that might be lurking.

OpenCode version

1.0.150

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

macOS 15.5

Terminal

VS Code terminal

Originally created by @jdanbrown on GitHub (Dec 12, 2025). Originally assigned to: @thdxr on GitHub. ### Description Bug 1: Shell commands are broken in message history - Send message `!date` → observe that `!` changes the input box into "Shell" mode, and then `date` is input into the box and run as a shell command (correct) - Press `up` to recall your last message → `date` is recalled into the input box, but it isn't switched into `Shell` mode, so when you send it it's incorrectly sent as a message to the model instead of as a command to the shell Bug 2: Shell commands are broken in `opencode run` - `opencode run '!date'` → sends the string `!date` to the model instead of running `date` as a shell command Is the fancy switch into `Shell` mode actually worthwhile, or would it be better overall to remove that and just interpret messages that start with `!` as shell commands? That would be one way to fix both of these issues by doing less, as well as any potential other issues that might be lurking. ### OpenCode version 1.0.150 ### Steps to reproduce _No response_ ### Screenshot and/or share link _No response_ ### Operating System macOS 15.5 ### Terminal VS Code terminal
yindo added the bug label 2026-02-16 17:40:25 -05:00
yindo closed this issue 2026-02-16 17:40:25 -05:00
yindo commented 2026-02-16 17:40:25 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Dec 12, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #2006: Shell commands are not stored in message history (directly addresses the message history recall problem)
  • #5310: Shell mode (! command) doesn't work on Windows (related shell command execution issues)
  • #4671: shell mode (!) is broken on Windows Powershell (Windows-specific shell execution)
  • #3213: opencode run and TUI exits hang on v0.15+ (related to opencode run command issues)
  • #4968: Shell sessions losing $PATH value from parent shell (environment inheritance for shell commands)
  • #2202: PATH is not inherited from invoking shell (similar environment inheritance issue)

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Dec 12, 2025): This issue might be a duplicate of existing issues. Please check: - #2006: Shell commands are not stored in message history (directly addresses the message history recall problem) - #5310: Shell mode (! command) doesn't work on Windows (related shell command execution issues) - #4671: shell mode (`!`) is broken on Windows Powershell (Windows-specific shell execution) - #3213: `opencode run` and TUI exits hang on v0.15+ (related to `opencode run` command issues) - #4968: Shell sessions losing $PATH value from parent shell (environment inheritance for shell commands) - #2202: PATH is not inherited from invoking shell (similar environment inheritance issue) Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:40:25 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 12, 2025):

Yeah run doesn't support shell mode, not sure how that'd work either since it just loads things into context, it doesn't trigger inference

@rekram1-node commented on GitHub (Dec 12, 2025): Yeah run doesn't support shell mode, not sure how that'd work either since it just loads things into context, it doesn't trigger inference
yindo commented 2026-02-16 17:40:25 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 12, 2025):

The other part is a bug tho

@rekram1-node commented on GitHub (Dec 12, 2025): The other part is a bug tho
yindo commented 2026-02-16 17:40:25 -05:00
Author
Owner
Copy Link
Copy Source

@jdanbrown commented on GitHub (Dec 15, 2025):

Thanks! Confirmed working in 1.0.159.

@jdanbrown commented on GitHub (Dec 15, 2025): Thanks! Confirmed working in 1.0.159.
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 bug
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#3510
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?