Composer 2.0 uses /usr/bin/<command> instead of just <command>

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When in agent mode executing a task, the generated commands would be in the form of /usr/bin/grep instead of plain grep.
This generates friction with allowlists and other possible user settings.

Steps to Reproduce

Ask the agent to work on a task with console tools enabled, eventually when running a command will use the long absolute path form instead of the simple form.

Screenshots / Screen Recordings

image (20).png

Operating System

MacOS

Version Information

Version: 2.7.0-pre.87.patch.0 (Universal)
VSCode Version: 1.105.1
Commit: b61848202de5fae8f5828fbbf9c50083eef90e40
Date: 2026-03-19T02:04:14.344Z
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

For AI issues: which model did you use?

Composer 2 Fast

For AI issues: add Request ID with privacy disabled

Company enforce privacy enabled.

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report.

The issue is that the Composer 2 Fast model decides on its own to use absolute paths instead of bare command names, and the allowlist matches the command by the first word exactly as-is. So grep in the allowlist won’t cover /usr/bin/grep.

Two workarounds for now:

  1. Manually add /usr/bin/grep, /usr/bin/sort, etc. to the allowlist (hacky, but it works).
  2. Add a project rule like: “When running terminal commands, use bare command names (e.g. grep, sort) instead of absolute paths (e.g. /usr/bin/grep).”

I’ve logged this with the team. Let me know if the rules workaround helped.

7

yeah, workarounds work, but in a 500 lines allowlist not only “breaks” compatibility with other models, its tedious.
Project rule helps sometimes

1 Like
8

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