Completed session tool cards accumulate below the active conversation
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Short summary
Completed session-tool calls such as Read session <session> accumulate below the latest user and assistant messages in long conversations. This displaces the active conversation upward and makes the user repeatedly scroll back to find it.
Affected version or release
1.0.84-5
Installation context
Windows, GitHub Copilot desktop app, long interactive chat coordinating multiple project sessions.
What happened?
After the agent reads or receives results from several other sessions, each completed operation remains visible as a separate tool card below the conversation. Repeated reads of the same session create many nearly identical cards.
The active user/assistant exchange is therefore no longer at the bottom of the transcript. The user has to scroll upward past a long block of tool activity to find the conversation.
Steps to reproduce
- Open a long interactive chat in the GitHub Copilot desktop app.
- Create or coordinate multiple project sessions.
- Let the current chat read results or status from those sessions repeatedly.
- Observe multiple
Read session <session>cards appearing below the latest conversation.
Expected behavior
- Tool executions should stay associated with the assistant turn that initiated them.
- Completed tool groups should collapse by default, especially repeated reads of the same session.
- The active conversation should remain at the bottom of the transcript.
- Failed and completed tool calls should remain inspectable without permanently occupying most of the conversation surface.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the GitHub Copilot desktop app using a long interactive chat that repeatedly reads or receives results from multiple sessions. Trace how completed session-tool calls are rendered below the latest user and assistant messages, then verify that tool groups remain inspectable while the active conversation stays at the bottom and repeated reads do not consume most of the transcript.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100