GitHub Copilot CLI session appeared to continue consuming AI credits after all visible tasks were completed.

Summary

GitHub Copilot CLI session appeared to continue consuming AI credits after all visible tasks were completed.

Environment

• GitHub Copilot CLI version: 1.0.75
• Mode: Interactive CLI session
• Session limit enabled: No
• Observed behavior: Session showed approximately 97.8% AI credit usage after the visible tasks completed. No further user prompts or interactions were made. Later, the session reached 100%.

Expected behavior

After all visible tasks are complete and no user interaction occurs, AI credit usage should either remain stable or the CLI should clearly indicate that background work is still running and consuming credits.

Actual behavior

The session moved from approximately 97.8% to 100% without additional user interaction.

Question

Is this expected due to final response accounting, subagent completion, or background compaction? If so, can the CLI expose clearer status so users can distinguish between:

1. truly idle waiting-for-input state, and
2. background/session-finalization work that may still consume AI credits?

Supporting context

GitHub documentation says session limits include model calls, subagents, and background work like compaction, and that session limits are soft caps because usage is only known after a response returns.

首先使用交互式会话在 GitHub Copilot CLI 1.0.75 中复现该行为，然后在可见任务完成且没有进一步提示后监控 credit 使用情况。将观察到的转换与文档中对模型调用、subagents 和后台压缩的处理进行比较；完成意味着任务后的使用情况得到解释，并且能够清楚地区分空闲状态或后台状态。