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 field for new message covers existing messages #1318

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

Originally created by @matthewryanscott on GitHub (Aug 15, 2025).

Originally assigned to: @adamdotdevin on GitHub.

I'm reporting this as a new bug since it seems to be a recently-introduced issue, and different from the issue discussed in the main description of #1098. I don't remember noticing the input field covering up the output until a recent release.

The input field for new message covers existing messages, so if I go over 2-3 lines, it hides a part of the output. The more I type, the less I can see. This is probably due to absolute positioning from bottom of viewport, so it might make sense to create a "shadow message" element in the output that replicates the height of our input message, allowing the output to be scrolled all the way to the bottom instead of remaining pinned down.

Originally posted by @tomoglavas in #1098

I have tested this with opencode 0.5.2 on MacOS using both iTerm2 and ghostty.

Originally created by @matthewryanscott on GitHub (Aug 15, 2025). Originally assigned to: @adamdotdevin on GitHub. I'm reporting this as a new bug since it seems to be a recently-introduced issue, and different from the issue discussed in the main description of #1098. I don't remember noticing the input field covering up the output until a recent release. > The input field for new message covers existing messages, so if I go over 2-3 lines, it hides a part of the output. The more I type, the less I can see. This is probably due to absolute positioning from bottom of viewport, so it might make sense to create a "shadow message" element in the output that replicates the height of our input message, allowing the output to be scrolled all the way to the bottom instead of remaining pinned down. _Originally posted by @tomoglavas in [#1098](https://github.com/sst/opencode/issues/1098#issuecomment-3191699679)_ --- I have tested this with opencode 0.5.2 on MacOS using both iTerm2 and ghostty.
yindo closed this issue 2026-02-16 17:30:25 -05:00
yindo commented 2026-02-16 17:30:25 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Aug 15, 2025):

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

  • #1098: Copy pasting large text makes scrolling impossible - related to input field scrolling issues
  • #1639: Can't stay scrolled to top in some cases - similar scrolling behavior problems
  • #1715: Cannot scroll up when response is streaming - scrolling issues with UI positioning
  • #1526: Pasting something big causes UI issues - input field causing display problems
  • #1844: Long file names in chat input box wrap weird - input box display issues

Feel free to ignore if none of these address your specific case of the input field covering messages with absolute positioning.

@github-actions[bot] commented on GitHub (Aug 15, 2025): This issue might be a duplicate of existing issues. Please check: - #1098: Copy pasting large text makes scrolling impossible - related to input field scrolling issues - #1639: Can't stay scrolled to top in some cases - similar scrolling behavior problems - #1715: Cannot scroll up when response is streaming - scrolling issues with UI positioning - #1526: Pasting something big causes UI issues - input field causing display problems - #1844: Long file names in chat input box wrap weird - input box display issues Feel free to ignore if none of these address your specific case of the input field covering messages with absolute positioning.
yindo commented 2026-02-16 17:30:25 -05:00
Author
Owner
Copy Link
Copy Source

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

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
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#1318
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?