anomalyco / anomalyco/opencode

[FEATURE]: Sticky headers for my prompt

Open
#39,833 2 comments 0 reactions 1 assignee View on GitHub

@simonklee is already working on this.

Since Jul 31, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

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

Current Situation

I type a prompt, that sometimes leads to a lot of output, sometimes over a long period of time as the agent works, to the terminal. A few minutes (or longer) later I come back and try to re-establish my own context as to "what did I ask it to do, and what is the response".

Opencode does great summaries at the end, but there is a lot of output sometimes between the prompt and the summary, and it's non-trivial to scroll back and find my original request to understand the report in context.

I do like the colored sidebar marker beside the prompt and

Suggestion

Use "sticky headers" like in some mobile app UIs, so instead of scrolling my prompt off screen, it sticks to the top of the text areas and the output starts to scroll under it.

Here is a video I found showing this in a mobile context, if that description is not clear:
https://www.youtube.com/watch?v=rCMr6BctEK4

if you scroll down the text through the history, when the prompt's location comes back into view, it would resume it's natural position within the history. I'm open to what would be displayed then, the previous header "stuck" at the top of the natural history of the output of the previous prompt. I'd incline towards the normal history...headers only stick when scrolling up and about to go off screen, then resume their position when scrolling down.

If we are in the output of a previous promp't section, changing scrolling direction to scroll up again, we'd "stick" that prompt to the top of the screen again.

Only one prompt would ever be "stuck" at the top.

If the prompt that is "stuck" is very long, then we probably need to put a cap on the lines it occupies and elipsize it. I'd show some of the start of the prompt and the end and elipsize as needed the middle portion.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.