Hey, thanks for the report. This is a known issue with URL parsing in deeplinks. It’s already been reported and the team is aware.
Also, looks like you reported the same thing about a month ago: Parsing issues with Deeplinks
The issue is in how Cursor decodes URL parameters. Some valid prompts are incorrectly marked as invalid. The team is working on a fix, but there’s no ETA yet.