Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Completed session tool cards accumulate below the active conversation

未关闭
#3,875 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
desktop, frontend

调研方向

在 GitHub Copilot desktop app 中,使用一个反复读取或接收多个会话结果的长交互式聊天来复现该问题。跟踪已完成的 session-tool calls 如何显示在最新的用户消息和助手消息下方,然后验证工具组仍可检查,同时活动对话保持在底部,并且重复读取不会占用大部分转录内容。

由索引模型根据 Issue 内容生成。

描述

triage
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
  1. Open a long interactive chat in the GitHub Copilot desktop app.
  2. Create or coordinate multiple project sessions.
  3. Let the current chat read results or status from those sessions repeatedly.
  4. 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

主要语言
没有语言数据
星标
2.1k
派生
157
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/app 的其他 Issue

查看 github/app 的全部 Issue

相似的 Issue

更多 Desktop Dev Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。