Work around schema parsing issue in Cursor #18
Merged
Conversation
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
gmethvin
force-pushed
the
cursor-schema-workaround
branch
from
0597588 to
badbba9
Compare
andrewboni
reviewed
Nov 25, 2025
andrewboni
approved these changes
Nov 25, 2025
gmethvin
force-pushed
the
cursor-schema-workaround
branch
from
badbba9 to
8ccb3db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cursor appears to have a bug with how it handles JSON schemas with union types, which causes an error for the
identifierin the snippet schema when trying to call the relevant tools.Work around this by accepting a string in the schema instead.