Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
Cursor AI consistently encounters processing issues and errors when handling SVG code, particularly during code reimplementation attempts. These issues manifest as:
Extended processing times (significantly longer than normal operations)
Tool errors appearing in the UI
Processing hangs and failures
IDE becomes unresponsive during SVG processing
Continuous loops of generating response, timing out, and getting tool errors in composer UI
The issue appears specific to SVG handling, while other code operations work as expected. The problem persists across different sessions with no clear pattern for successful vs. failed attempts.
Steps to Reproduce
- Open a composer session in Cursor AI
- Attempt to modify or reimplement existing SVG code
(Specific example: implementing a CSS animation in a React index.tsx for an SVG file in the directory) - Wait for processing
- Observe tool error in UI
- Watch as it loops through generating a response, timing out, and getting a tool error in the composer UI
Expected Behavior
Normal processing times comparable to other code operations
Successful SVG code implementation
Responsive UI during SVG processing
Clear, specific error messages instead of generic “tool error”
Proper error explanation without needing to use prompt credits to force generation explanation
Operating System
Windows 10/11
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.10
VSCode Version: 1.93.1
Commit: ae296fde8115b123d8ce516cdfedf697fc577660
Date: 2025-01-02T09:19:53.599Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631
Additional Information
mpact and Technical Details:
Severity: High - Blocks SVG-related development tasks
Forces developers to use workarounds or avoid SVG tasks
No specific error codes provided
Limited debugging information
Higher failure rates with complex SVG structures
Issue occurs consistently with SVG-related operations
Current workarounds:
Implementing SVG code manually
Using alternative tools for SVG manipulation
Avoiding complex SVG operations in Cursor AI
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
but this is an actual bug. It seems like if it’s trying to implement svg code within an existing typescript file Cursor has tooling errors in the Composer UI. But when it comes to the llm/Cursor directly working on the SVG, no matter how complex, it works (and usually with good results).