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

[FEATURE]: Make the last user prompt sticky when scrolling #3290

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

Originally created by @conradkoh on GitHub (Dec 4, 2025).

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

When scrolling, currently the user's prompt scrolls up with only the title being sticky. For long threads, it would be nice if we could get the last user's prompt to be sticky, similar to how cursor does it.

This is especially useful if I am working on multiple tasks at once and I want to remember how to verify what the AI did relative to what I asked.

Currently I would need to scroll all the way up and try to find out what was last asked before I can go ahead and test.

Originally created by @conradkoh on GitHub (Dec 4, 2025). ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request When scrolling, currently the user's prompt scrolls up with only the title being sticky. For long threads, it would be nice if we could get the last user's prompt to be sticky, similar to how cursor does it. This is especially useful if I am working on multiple tasks at once and I want to remember how to verify what the AI did relative to what I asked. Currently I would need to scroll all the way up and try to find out what was last asked before I can go ahead and test.
yindo added the discussion label 2026-02-16 17:39:32 -05:00
yindo commented 2026-02-16 17:39:32 -05:00
Author
Owner
Copy Link
Copy Source

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

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

  • #1967: Input field for new message covers existing messages - addresses the same core problem of message visibility being obstructed by the input field
  • #3333: Message entry covers OpenCode response - describes the same issue where long prompts hide previous LLM output
  • #4353: Long multi line prompt hides output - similar issue about prompts hiding output (now closed)
  • #3642: Missing ability to open editor for history - related feature request about accessing previous context while composing new prompts
  • #5016: Editing prompts in editor should include conversation history - related feature addressing context visibility needs

Feel free to ignore if your request has a different focus than these issues.

@github-actions[bot] commented on GitHub (Dec 4, 2025): This issue might be a duplicate of or related to existing issues. Please check: - #1967: Input field for new message covers existing messages - addresses the same core problem of message visibility being obstructed by the input field - #3333: Message entry covers OpenCode response - describes the same issue where long prompts hide previous LLM output - #4353: Long multi line prompt hides output - similar issue about prompts hiding output (now closed) - #3642: Missing ability to open editor for history - related feature request about accessing previous context while composing new prompts - #5016: Editing prompts in editor should include conversation history - related feature addressing context visibility needs Feel free to ignore if your request has a different focus than these issues.
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 discussion
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#3290
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?