Terminal commands in Agent

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m not sure if this is a bug or just my lack of understanding… essentially for the past few days I’ve been working on a few Laravel projects with Agent and it’s been great. However today, when it’s made changes, it’s now asking me to run terminal commands like ./vendor/bin/sail artisan migrate.
Also it seems to struggle with commands like ./vendor/bin/sail up -d as well, and in the Agent Terminal I can see it say that “Docker is not running”. If I run the exact command myself in a standard Terminal window, it runs it fine.

As I say, I’m pretty sure it’s something I’m doing wrong so hopefully you can point me in the right direction!

Steps to Reproduce

Just running the commands mentioned above.

Expected Behavior

Up until today, it has been running those commands fine so I’d have thought it would continue to run them.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.46 (Universal)
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

grok-code-fast-1, gpt-5

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report. It’s most likely because the agent’s terminal runs in a non‑interactive shell and doesn’t load your .zshrc/.bashrc where Docker paths are usually set.

Try this first:

  1. Enable “Legacy Terminal Tool” in Cursor settings
  2. Restart Cursor
  3. Test your Laravel Sail commands via the agent

Let me know if enabling Legacy Terminal Tool helps.

1 Like
3

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