Wrong file extension issue

Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

I wasn’t sure what to put this under but it seems Cursor consistently doesn’t use the right extension when writing viralog. Instead of *.sv, which is the file extension in EDAplayground, it used *.v

Steps to Reproduce

tell the AI to write some Varilog, it’ll (likely) use *.v

Expected Behavior

unless it’s a legacy thing withing Varilog itself, the extension should be *.sv

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.17.6-zen1-1-zen

For AI issues: which model did you use?

I had it set to auto so TBH I don’t know

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. You’re right, .sv is the standard extension for SystemVerilog and .v is the older extension for Verilog.

To help us look into this further, could you:

  • Share the exact prompt you used when asking the AI to write Verilog code
  • Get the Request ID for one of these responses: click the three dots in the chat (top right) → Copy Request ID
  • Let me know which model was used (you can see this in the chat response)

As a workaround, you can guide the AI to use the correct extension by adding a .cursorrules file to the project root with something like:

When generating Verilog/SystemVerilog code,
always use the .sv file extension instead of .v

Let me know if this workaround helps.

3

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.