The IntelliJ IDEA Cursor plugin does not have a setting which allows all tool access/terminal command execution.
There is an “always allow” option for each command, however the generated commands usually include filenames and switches, ensuring they are almost always unique, and do not match future commands.
Given the above, it’s quite cumbersome to use, especially for long-running tasks. Continuous supervision is required, and tasks will time out if a command isn’t approved/rejected quickly enough.
If possible, add a mode which allows commands/tools to be executed without approval. If safety is a concern, allow the user to whitelist common tasks (e.g. running a test, type checker or linter).
Hey, thanks for the feature request. This is a known issue. In the current ACP plugin, the allowlist matches the exact command including all args and flags, so in practice it almost never triggers for repeated commands. We’ve logged it on our side.
In Cursor IDE, Auto-run is being actively developed right now, including an LLM classifier that decides what’s safe to auto-run, but these capabilities haven’t been brought to the IntelliJ ACP plugin yet. I can’t share an ETA for adding this to ACP.
If there’s an update, I’ll reply in the thread. Votes and reports from other ACP users will help us prioritize it, so if anyone else hits this, please post it here.
It would definitely be beneficial to make it so the IntelliJ Cursor plugin doesn’t require supervision. The constant stopping and asking me if it can execute a command is annoying. It is asking me for permission to execute pwd, come on now, that is annoying.
So consider this a vote for the feature OP is asking for.
Hey @spiritualized, circling back to the thread with an honest update.
After review, this feature isn’t prioritized yet. In the JetBrains ACP integration, there’s still no mode to run commands without approval, and I can’t share a timeline for it. Auto-run with the classifier is being developed in Cursor IDE itself, but those capabilities haven’t been brought over to the ACP plugin yet.
I get that for long tasks, the current per-command approval really gets in the way, and yeah, approving pwd is overkill. Reports from JetBrains users help us prioritize this, so votes in the thread do count.
If anything changes, I’ll post an update here. If this is still an issue on the latest version, feel free to start a separate thread with details and we’ll take a fresh look.