Support custom status line and context-window usage in the Copilot desktop app
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
Summary
The native GitHub Copilot desktop app does not render the custom status line or context-window footer configured in ~/.copilot/settings.json, even though the same configuration works in the terminal-hosted Copilot CLI.
Environment
- OS: Windows
- GitHub Copilot desktop app:
1.1.19 - Desktop executable:
C:\Users\<user>\AppData\Local\Programs\GitHub Copilot\github.exe - GitHub Copilot CLI:
1.0.84-4
Configuration
{
"statusLine": {
"type": "command",
"command": "powershell.exe -NoProfile -ExecutionPolicy Bypass -File \"C:\\Users\\<user>\\.copilot\\statusline.ps1\""
},
"footer": {
"showContextWindow": true,
"showCustom": true
}
}
The configured PowerShell command reads the status payload from stdin and prints context-token usage.
Steps to reproduce
- Configure
statusLine.command,footer.showCustom, andfooter.showContextWindowin~/.copilot/settings.json. - Start Copilot CLI from PowerShell by running
copilot. - Send a prompt and observe that the custom context usage (for example,
49.5k/? tokens) appears in the terminal footer. - Close the terminal session and launch the native desktop app using
github.exe. - Open a session and send a prompt.
Actual behavior
The desktop app does not display the custom status-line output or a context-window usage indicator. The command itself is valid and works in the terminal CLI.
Expected behavior
The desktop app should either:
- honor
statusLine.commandand the relevantfooter.*settings, or - provide a native equivalent that continuously shows used/remaining context-window capacity for the active session.
Why this matters
Context-window visibility helps users decide when to summarize, checkpoint, or start a new session before earlier context is compacted or lost. Users moving between the terminal CLI and native desktop app should have equivalent visibility into session context usage.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
首先比较通过 github.exe 启动的桌面应用与终端 Copilot CLI 针对 ~/.copilot/settings.json 的行为。跟踪 statusLine.command、footer.showCustom 和 footer.showContextWindow 的处理方式,然后验证桌面会话是否渲染配置的输出,或者像 CLI 一样持续显示上下文窗口的使用情况。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- powershell
- 领域
- cli, desktop
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100