Tool/function calls intermittently emit malformed invocation markup (court / <invoke>) and silently no-op
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
This issue was generated by the GitHub Copilot CLI agent itself (Claude Opus 4.8), not written by a human. The human user may add further details later.
Environment
- Copilot CLI version: 1.0.82
- Model: Claude Opus 4.8 (claude-opus-4.8)
- OS: Windows
- Shell: PowerShell
Summary
During a long interactive session, a significant fraction of the agent's tool calls are emitted in a malformed format — the message contains a stray literal token (court) followed by <invoke name="..."> markup instead of a properly-formed function call. When this happens the tool does not execute; no command runs and no output is produced. Retrying the identical call usually succeeds on the 2nd–4th attempt.
Impact
- Frequent wasted turns: the user repeatedly has to prompt "your tool call failed / is malformed, redo it."
- Severe slowdown of multi-step workflows (e.g. git history surgery, build/test loops) where nearly every step needed 1–3 retries.
- Erodes trust; in this session the user considered the agent effectively broken.
Observed pattern
- Prevalence increases as the session/context grows large (this session was very long, with extensive tool use).
- Especially frequent on
powershelltool calls that use here-strings/multi-line scripts, though it also affects simple calls. - The malformed output looks like a leaked internal call wrapper rather than a valid tool invocation.
Expected
Every tool invocation is emitted in the correct function-call format and executes reliably, regardless of session length.
Actual
Calls intermittently render as literal court + <invoke …> text and are dropped (no execution, no error surfaced to the tool layer).
Workarounds tried
- Re-issuing the same call in the exact correct format (works, but only after failed attempts).
- Keeping call blocks minimal / avoiding here-strings reduces but does not eliminate it.
Notes
No custom tools involved in the failures; occurs with built-in powershell/git operations. Repro is nondeterministic but recurrent within a single long session.
Text below is added by @MortenBoysen, the human operator.
As an example of a session where this happens, below I have pasted in the part of the session where Copilot CLI had to submit this bug report:
Let me write the body to a temp file (avoids quoting issues), then create the issue with the bug label.
Create copilot-cli-bug.md +33
Shell Create the bug report issue with bug label 2 lines…
Set-Location C:\git\repo $body = "C:\Users\Morten Boysen\AppData\Local\Temp\copilot-cli-bug.md" gh issue create --repo github/copilot-cli --title…
Thought for 1s
The bug label doesn't exist there. Let me check what labels are available.
court
Set-Location C:\git\repo
gh label list --repo github/copilot-cli --limit 40 2>&1 | Select-Object -First 40
List available labels in target repo
> tool call failed again
court
Set-Location C:\git\repo
gh label list --repo github/copilot-cli --limit 40 2>&1 | Select-Object -First 40
List available labels in target repo
> tool call failed again
court
Set-Location C:\git\repo; gh label list --repo github/copilot-cli --limit 40 2>&1 | Select-Object -First 40
List available labels in target repo
> tool call failed again
$ Shell List available labels in target repo 31 lines…
Set-Location C:\git\repo; gh label list --repo github/copilot-cli --limit 40 2>&1 | Select-Object -First 40
Thought for 3s
No bug label exists. Best-matching labels are area:tools ("...tool call behavior") and area:context-memory (prevalence grows with context size). Submitting with those.
court
Set-Location C:\git\repo
$body = "C:\Users\Morten Boysen\AppData\Local\Temp\copilot-cli-bug.md"
gh issue create --repo github/copilot-cli --title "Tool/function calls intermittently emit malformed invocation markup (court / ) and silently no-op" --body-file $body --label "area:tools" --label "area:context-memory" 2>&1
Create the bug report with area labels
> tool call failed again
court
Set-Location C:\git\repo
$body = "C:\Users\Morten Boysen\AppData\Local\Temp\copilot-cli-bug.md"
gh issue create --repo github/copilot-cli --title "Tool/function calls intermittently emit malformed invocation markup (court / ) and silently no-op" --body-file $body --label "area:tools" --label "area:context-memory" 2>&1
Create the bug report with area labels
> tool call failed again
$ Shell Create the bug report with area labels 2 lines…
Set-Location C:\git\repo $body = "C:\Users\Morten Boysen\AppData\Local\Temp\copilot-cli-bug.md" gh issue create --repo github/copilot-cli --title…
Submitted successfully.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
没有指定源文件或测试。首先在内置的 PowerShell 和 git 工具路径中重现格式错误的调用,并比较短会话和长会话中的短命令与多行命令。完成标准是始终输出有效的 function-call 格式、命令能够执行,并且失败会显示错误,而不是静默丢弃调用。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- git, powershell, shell
- 领域
- cli, developer-experience, tooling
- Issue 类型
- 缺陷
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100