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

Input text displays in terminal instead of input box, Enter creates newline instead of submitting (V 1.0.20) #2714

New Issue
Closed
opened 2026-02-16 17:36:55 -05:00 by yindo · 9 comments
yindo commented 2026-02-16 17:36:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @nikitalobanov12 on GitHub (Nov 8, 2025).

Description

After updating to the newest version, the input handling appears to be broken. Text input is being rendered directly in the terminal display area instead of in the dedicated input box, and pressing Enter creates a newline in the terminal rather than submitting the request.

I ran the old version with bun x opencode-ai@0.15.31 and everthing there works fine, sometimes terminal escape sequences get dumped on the screen when I'm in the app as well but I can't recreate that problem

I've attached a screenrecording that shows this problem since I'm not too sure how to describe it

https://github.com/user-attachments/assets/474f2462-e78a-4838-9c6c-973648b78f46

OpenCode version

1.0.20

Steps to reproduce

ghostty --version                                                                          ~
Ghostty 1.2.3-arch2

Version
  - version: 1.2.3-arch2
  - channel: tip
Build Config
  - Zig version   : 0.14.1
  - build mode    : builtin.OptimizeMode.ReleaseFast
  - app runtime   : apprt.Runtime.gtk
  - font engine   : font.main.Backend.fontconfig_freetype
  - renderer      : renderer.generic.Renderer(renderer.OpenGL)
  - libxev        : io_uring
  - kernel version: 6.17.7-arch1-1
  - desktop env   : other
  - GTK version   :
    build         : 4.20.2
    runtime       : 4.20.2
  - libadwaita    : enabled
    build         : 1.8.1
    runtime       : 1.8.1
  - libX11        : enabled
  - libwayland    : enabled

Screenshot and/or share link

No response

Operating System

6.17.7-arch1-1

Terminal

Ghostty but same issue on Alacritty and Kitty

Originally created by @nikitalobanov12 on GitHub (Nov 8, 2025). ### Description After updating to the newest version, the input handling appears to be broken. Text input is being rendered directly in the terminal display area instead of in the dedicated input box, and pressing Enter creates a newline in the terminal rather than submitting the request. I ran the old version with `bun x opencode-ai@0.15.31` and everthing there works fine, sometimes terminal escape sequences get dumped on the screen when I'm in the app as well but I can't recreate that problem I've attached a screenrecording that shows this problem since I'm not too sure how to describe it https://github.com/user-attachments/assets/474f2462-e78a-4838-9c6c-973648b78f46 ### OpenCode version 1.0.20 ### Steps to reproduce ```shell ghostty --version ~ Ghostty 1.2.3-arch2 Version - version: 1.2.3-arch2 - channel: tip Build Config - Zig version : 0.14.1 - build mode : builtin.OptimizeMode.ReleaseFast - app runtime : apprt.Runtime.gtk - font engine : font.main.Backend.fontconfig_freetype - renderer : renderer.generic.Renderer(renderer.OpenGL) - libxev : io_uring - kernel version: 6.17.7-arch1-1 - desktop env : other - GTK version : build : 4.20.2 runtime : 4.20.2 - libadwaita : enabled build : 1.8.1 runtime : 1.8.1 - libX11 : enabled - libwayland : enabled ``` ### Screenshot and/or share link _No response_ ### Operating System 6.17.7-arch1-1 ### Terminal Ghostty but same issue on Alacritty and Kitty
yindo added the opentuibug labels 2026-02-16 17:36:55 -05:00
yindo closed this issue 2026-02-16 17:36:55 -05:00
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 8, 2025):

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

  • #4046: Similar input handling issues in v1.0 with Ghostty terminal where keybindings don't work as expected
  • #1505: Enter key behavior problems and input handling issues in the TUI
  • #3927: Input handling regression in v1.0.24 where multi-line input is fragmented
  • #3699: TUI input problems in v1.0.7 specifically with Ghostty terminal
  • #344: Enter and newline key issues with Ghostty terminal in earlier versions

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

@github-actions[bot] commented on GitHub (Nov 8, 2025): This issue might be a duplicate of existing issues. Please check: - #4046: Similar input handling issues in v1.0 with Ghostty terminal where keybindings don't work as expected - #1505: Enter key behavior problems and input handling issues in the TUI - #3927: Input handling regression in v1.0.24 where multi-line input is fragmented - #3699: TUI input problems in v1.0.7 specifically with Ghostty terminal - #344: Enter and newline key issues with Ghostty terminal in earlier versions Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@Beloin commented on GitHub (Nov 8, 2025):

If you scroll or do something else, TUI is not interpreting

@Beloin commented on GitHub (Nov 8, 2025): If you scroll or do something else, TUI is not interpreting
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 9, 2025):

Can yall try the latest version? We addressed a lot of issues recently?

@Beloin what version r u on?

@rekram1-node commented on GitHub (Nov 9, 2025): Can yall try the latest version? We addressed a lot of issues recently? @Beloin what version r u on?
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@Beloin commented on GitHub (Nov 9, 2025):

@rekram1-node its something weird. Sometimes it works, but sometimes it just bugs and dont undestand inputs.

I am using with neovim, but TUI client also shows the same problems.

In neovim
Image

in opencode TUI
Image

Version:

Image
@Beloin commented on GitHub (Nov 9, 2025): @rekram1-node its something weird. Sometimes it works, but sometimes it just bugs and dont undestand inputs. I am using with neovim, but TUI client also shows the same problems. In neovim <img width="738" height="1018" alt="Image" src="https://github.com/user-attachments/assets/a34e2433-f38a-445a-a102-ebaa654f7fa0" /> in opencode TUI <img width="1920" height="1038" alt="Image" src="https://github.com/user-attachments/assets/702d81e2-dfae-4f57-bb7b-f42b35b16963" /> Version: <img width="497" height="39" alt="Image" src="https://github.com/user-attachments/assets/542ef40e-85af-4384-b157-b09b58b01a0b" />
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 9, 2025):

@Beloin can you upgrade to latest tho? Like I said I think we fixed some of these issues already

@rekram1-node commented on GitHub (Nov 9, 2025): @Beloin can you upgrade to latest tho? Like I said I think we fixed some of these issues already
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@Beloin commented on GitHub (Nov 9, 2025):

Sorry, I thought it was already the latest version. I will try tomorrow ( already 2Am at my local time ) and notify this thread. Also I will try to use the compiled binary, or build it. AUR package is weird sometimes

@Beloin commented on GitHub (Nov 9, 2025): Sorry, I thought it was already the latest version. I will try tomorrow ( already 2Am at my local time ) and notify this thread. Also I will try to use the compiled binary, or build it. AUR package is weird sometimes
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@nikitalobanov12 commented on GitHub (Nov 9, 2025):

It's fixed for me on the new version

I had it installed via yay from the aur package & it was telling me that 1.0.20 was the latest version, sorry about that

@nikitalobanov12 commented on GitHub (Nov 9, 2025): It's fixed for me on the new version I had it installed via yay from the aur package & it was telling me that 1.0.20 was the latest version, sorry about that
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Nov 9, 2025):

no problem :)

@rekram1-node commented on GitHub (Nov 9, 2025): no problem :)
yindo commented 2026-02-16 17:36:56 -05:00
Author
Owner
Copy Link
Copy Source

@Beloin commented on GitHub (Nov 9, 2025):

It fixed also for me. Sorry for the confusion

@Beloin commented on GitHub (Nov 9, 2025): It fixed also for me. Sorry for the confusion
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 opentui
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#2714
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?