In Cursor 2 version the code is shown as text it doesn’t have any color or highlight which cause confusion with texts and over all it is not good.
I reinstalled older version and it was fixed
Hey, thanks for the report. This looks like a known issue affecting syntax highlighting in chat code blocks for certain languages in Cursor 2.0+.
To help confirm this is the same issue, could you share:
- Your current Cursor version (Help > About Cursor > Copy)
- Which programming languages are showing as plain text?
- Is this happening in Chat/Agent responses specifically, or in your editor files?
The team is aware and investigating. As a temporary workaround, you can use an older version until this is fixed.
I was faced with this issue at latest version 2.0.69 . I was using Solidity and Move in agent responses part none of these languages syntax and highlight was support. But when I return to older version everything works great and correctly.
Actually, a quick correction - this isn’t a bug. Cursor (and VSCode) don’t include built-in syntax highlighting for Solidity and Move by default.
You’ll need to install language extensions:
Solidity: Open VSX Registry
Move: Open VSX Registry
Once installed, syntax highlighting should work correctly in the editor and in Agent chat responses. Most likely, the older setup worked because those extensions were already installed.
Let me know if installing the extensions resolves it.
I haven’t changed any extensions during upgrading to Cursor 2.0.69 . I have the same setup but newer cursor isn’t following syntax or highlight, on the other hand older version works perfectly with same extensions.
1 Like
I have just download and updated to the latest version 2.0.75 . But still the same problem exists can’t highlight and support the syntax
Thanks for the info, that’s very helpful.
1 Like
I’m having the same kind of issue
I don’t know why the problem can’t be fixed again the problem still exists in the new version of 2.0.77
@deanrie Please solve this problem, it is not user friendly. I have requested agent to fix it but still it doesn’t work and for both Solidity and Move this error happens.
Answer of agent :
1 Like
I don’t know why the problem exists in all the newer versions, and why this simple problem can’t be solve @deanrie
1 Like
Still no updates on this issue?
Updates are rolling out but not a fix in sight…
I am also confused why a simple problem can’t be solve, as we have seen multiple updated versions but can’t see any fix for this issue @deanrie
Replying here to avoid the thread closing…
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.