Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Resuming a long session scrolls very far back, scrollbar may or may not be draggable to return

Open
#4,894 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
linux, shell, zsh
Domain
cli

Research direction

Reproduce the issue in GitHub Copilot CLI 1.0.85 using a long chat, switching to another chat, then returning to it on zsh/Linux. Trace the session-resume scroll behavior and verify that returning to a long session leaves the view at its previous position or the most recent output without repeated scrolling.

Written by the indexing model from the issue text.

Description

triage
Describe the bug

When I am switching back to a long-lived session, the scrollbar takes me back halfway or almost to the beginning. I can see it scrolling up multiple times, as in it's not setting the scroll once, it's setting the scroll position erroneously multiple times on resume. It goes so far back that scrolling via mouse would take ages. My workaround is to waste tokens sending a "." then canceling it immediately to return to the bottom. The scrollbar can help but may or may not even be working.

Affected version

GitHub Copilot CLI 1.0.85

Steps to reproduce the behavior
  1. Have a long chat
  2. Switch to another chat
  3. Switch back to the long chat. it scrolls

This happens every single time for me.

Expected behavior

Resuming a session either stays where I was or takes me to the most recent output. I don't care which, I just want it to not take me somewhere random.

Additional context

Using zsh on linux

Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

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.

More from github/copilot-cli

All issues in github/copilot-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.