In Cursor Settings, the command allowlist displays the first 25 or so characters of the command. I have in my allowlist commands like /home/my-user/code/envs/my-project-name/pytest which do not display to the end.
Fix suggestions:
Easy: a simple tool tip on the commands
Better: an editable text file storing the allowlist
Even better: make that hierarchical so I can have both global and per-project allowlists.
Steps to Reproduce
Add a command longer than 30 characters to the allowlist, view in Cursor Settings.
Thanks for reporting this — it’s a confirmed bug. Long commands in the allowlist are truncated at ~25-30 characters with no way to see the full text (no tooltip on hover).
For now, if you need to verify what’s in your allowlist, you can check your Cursor settings JSON directly — the commands are stored in full there even though the UI truncates them.
Thanks. I’m using Cursor UI and it seems like there isn’t a straightforward way to see the settings in json format (perhaps in the CLI there is). Cursor itself suggested me an incantation to extract them from my ~/.config/Cursor/User/globalStorage/state.vscdb. I’d love to have them accessible via a text settings file.
Good catch — my suggestion about the settings JSON was imprecise. The command allowlist is stored in an internal database (state.vscdb), not in settings.json.
However, there is a text-based alternative you can use: create a file at ~/.cursor/permissions.json with your allowlist commands:
When this file exists and has entries, it takes precedence over the UI-managed allowlist. You can edit it with any text editor and it applies globally (not per-workspace). Cursor watches the file for changes, so edits take effect without restarting.