Message history corrupted after aborting an operation that hung

[dereklegenzoff]

Describe the bug

Copilot hung while trying to run npx create-next-app.

The issue seems to be that the CLI command returned an error and copilot wasn't able to handle the failure:

The directory llm-games-v2 contains files that could conflict:

IMPLEMENTATION_CHECKLIST.md
SPEC.md

Either try using a new directory name, ore remove the files listed above.

It may have also been that the command required user input to approve installing create-next-app, I'm not 100% sure.

I eventually had to abort the operation and when i tried again, the conversation history was messed up leading to model call failures:

Affected version

0.0.342 Commit: 69ac520

Steps to reproduce the behavior

1. Create a folder and add files to that folder with content in them
2. Run copilot
3. Have it scaffold a next.js app
4. Abort the operation
5. Try to resume

I tried to repo from scratch and copilot succeeds in other contexts but failed multiple times trying to do this in the original scenario.

Expected behavior

Ideally Copilot could gracefully handle the failure, show the error to the user, and work around it. It should also be easy to resume the conversation after aborting the failure.

Not seeing the CLI outputs makes it much harder to understand what's going on. Often the output shows "thinking" when it's really waiting for the CLI to finish.

Additional context

No response

[williammartin]

Thanks for the report, we fixed something in this area yesterday, but it appears you are already on the latest release 🤔 Definitely something for us to look into. In the meantime, could you try resuming the conversation with --continue or --resume and see whether that unblocks the conversation? There is some code that should try to clean this up.

[williammartin]

Often the output shows "thinking" when it's really waiting for the CLI to finish.

Does ctrl+r give you what you want?

[dereklegenzoff]

Thanks for the quick response and for the help!

In the meantime, could you try resuming the conversation with --continue or --resume and see whether that unblocks the conversation?

I don't have the conversation open any more, unfortunately. I was able to work around the issue eventually and had copilot keep hacking on the broader solution. I'm definitely not blocked but wanted to report the issue I ran into in case it was helpful.

Does ctrl+r give you what you want?

Ahh yeah the expanded content with ctrl+r is great! Definitely makes it easier to see what is going on. I somehow missed that was an option; i'll have that turned on from here on out.

[dereklegenzoff]

Just a heads up -- I ran into this issue again after aborting something. Same error with tool_use ids were found without tool_result blocks

I tried --resume this time and ran into the same error again. In case it's helpful, here are the request Id's from before the resume:

• C4BE:1181B3:18E947:1F3319:68F16A12
• C4BE:1181B3:18F74B:1F453A:68F16A13

And here are a couple from after the resume:

• C4F0:E4956:17AB25:1DE183:68F16AFC
• C4F0:E4956:17B69F:1DF05A:68F16AFD

Also got prompted to update to the latest version (0.0.343) and still saw the same error trying to resume after that. The request id after the update was C510:267558:1E33A8:259084:68F16B9C

[dereklegenzoff]

Interestingly, when i did copilot --continue instead of copilot --resume then i didn't hit the same error