Skip to content

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

Closed

Description

@jdanbrown

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

Activity

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Dec 12, 2025
  2. changed the title [-]Shell commands are broken in message history[/-] [+]Shell commands are broken in message history and in `opencode run`[/+] on Dec 12, 2025
  3. github-actions commented on Dec 12, 2025

    @github-actions
    Contributor

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

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

  4. rekram1-node commented on Dec 12, 2025

    @rekram1-node
    Contributor

    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

  5. removed
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Dec 12, 2025
  6. rekram1-node commented on Dec 12, 2025

    @rekram1-node
    Contributor

    The other part is a bug tho

  7. added a commit that references this issue on Dec 15, 2025
    6632987
  8. jdanbrown commented on Dec 15, 2025

    @jdanbrown
    ContributorAuthor

    Thanks! Confirmed working in 1.0.159.

  9. added a commit that references this issue on Dec 17, 2025
    334ebd9
  10. added a commit that references this issue on Dec 27, 2025
    b77826f
  11. added a commit that references this issue on May 5, 2026
    4b647c6
  12. added a commit that references this issue on Jun 14, 2026
    327a96e
  13. added a commit that references this issue on Jul 31, 2026
    bc1307b
  14. added a commit that references this issue on Sep 6, 2026
    46e97bb
  15. added a commit that references this issue on Sep 19, 2026
    bbb0f20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions