CopilotC-Nvim / CopilotC-Nvim/CopilotChat.nvim
Output just stops
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 3.7k
- Forks
- 171
- Avg merge
- 16h 26m
- Merged PRs (30d)
- 1
Description
I'm a new user of this plugin and like it a lot, especially for the glob feature, which allows me to define the project context. Maybe I'm doing something wrong, please help!
Observed behavior
AI response seems to be interrupted in the middle. The output just stops after running some tools. Also the spinner is no longer visible. If I press enter again, it continues, but I'm not sure if it just sends another response.
Expected behavior
AI response is fully printed.
Steps to reproduce
I can reproduce this with Neovim 0.12.2, using this minimal configuration:
require("paq")({
"savq/paq-nvim",
"https://github.com/nvim-lua/plenary.nvim",
"https://github.com/CopilotC-Nvim/CopilotChat.nvim.git",
})
require("CopilotChat").setup({
model = "claude-sonnet-4.6",
--trusted_tools = true,
trusted_tools = { "file", "glob", "grep", "gitdiff" },
})
- open chat with
CopilotChatToggle - enter the following prompt, or similar, which asks for a context of a few hundred source files:
@copilot #glob:{libabc,libx,liby/lib*,tools/z}/{inc,src}/**/*.{hpp,cpp,y,l}
Analyze the given source code. I want to implement a check in method someThing that makes ...la la la... Give a minimal implementation for such a check.
- after running for a few seconds and doing something, output stops here:
- 1911 Copilot (claude-sonnet-4.6) ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Tool calls:
glob:tooluse_xIwVq7tCmIekcAGZBw92rY
{
pattern = "libabc/inc/**/*.hpp"
}
glob:tooluse_19BzERV89XDQe3rEL6W298
{
pattern = "libx/inc/**/*.hpp"
}
glob:tooluse_XTNWr5LLUS6r0U9vjE76k8
{
pattern = "liby/lib*/inc/**/*.hpp"
}
1912
- 1913 User ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ gh to show help
│ 27300/168000 tokens used
│ 1914
│ 1915 #glob:tooluse_xIwVq7tCmIekcAGZBw92rY
│ 1916 #glob:tooluse_19BzERV89XDQe3rEL6W298
│ {
│ pattern = "libabc/inc/**/*.hpp"
│ }
│ 1917 #glob:tooluse_XTNWr5LLUS6r0U9vjE76k8
│ {
│ pattern = "libx/inc/**/*.hpp"
│ }
│ 1918
│ {
│ pattern = "liby/lib*/inc/**/*.hpp"
│ }
│ 1919
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
Start with the minimal Neovim configuration and reproduce the issue through CopilotChatToggle using the shown #glob prompt and trusted tools. Trace how the glob tool calls are handled after the response begins; done means the complete AI response is printed and the spinner remains correctly managed without requiring another Enter press.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100