Open
Conversation
cursor has some extension methods that we do not (yet) implement. When one comes in (e.g. _cursor/update_todos), the session hangs unless we send a response.
Contributor
Author
|
An example traffic session showing the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've been using this a fair bit over the last day and it generally works well.
Cursor has some extension points, and at least for
_cursor/update_todosthis caused the agent session to hang. I've implemented an error response to unknown messages, and this allows the session to proceed. It seems like an appropriate response in general. We can decide whether to support their custom extension points later.Fixes: #386
Checklist
M-x checkdocandM-x byte-compile-file.