When the agent goes to run a terminal command, it fails for the majority of tools, commands that aren’t standard. Basically, I can’t use my development environment for the Agent. Open the agent terminal isn’t also interactive to investigate.
Steps to Reproduce
Have custom environment variables and paths that required to be loaded depending on the project.
The agent needs to run commands in the project that requires any of these predefined in the shell/path, such as a company’s custom test runner
It will fail
Expected Behavior
It should run the terminal using the login shell. As it was working before the last update.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
$ direnv allow
zoxide: detected a possible configuration issue.
Please ensure that zoxide is initialized right at the end of your shell configuration file (usually ~/.zshrc).
If the issue persists, consider filing an issue at:
https://github.com/ajeetdsouza/zoxide/issues
Disable this message by setting _ZO_DOCTOR=0.
direnv: error .envrc file not found
$ ls -la | grep env
zoxide: detected a possible configuration issue.
Please ensure that zoxide is initialized right at the end of your shell configuration file (usually ~/.zshrc).
If the issue persists, consider filing an issue at:
https://github.com/ajeetdsouza/zoxide/issues
Disable this message by setting _ZO_DOCTOR=0.
$ rx "private context"
zoxide: detected a possible configuration issue.
Please ensure that zoxide is initialized right at the end of your shell configuration file (usually ~/.zshrc).
If the issue persists, consider filing an issue at:
https://github.com/ajeetdsouza/zoxide/issues
Disable this message by setting _ZO_DOCTOR=0.
(eval):1: command not found: rx
Thanks for reporting this issue. We’re working on a lot of terminal improvements in upcoming releases, but meanwhile can you see if any of these solutions help:
This happens to me as well. My host machine is macOS and when I use Cursor agent locally and asks it to open a terminal it can open a normal login interactive zsh terminal just like before, but now when I use agent in SSH remote dev environment it can only open a non interactive shell which doesn’t load most of the alias / commands like kubeswitch for me. This was not the case before I update cursor today.
My current cursor version:
Version: 1.6.23
VSCode Version: 1.99.3
Commit: 9b5f3f4f2368631e3455d37672ca61b6dce85430
Date: 2025-09-15T21:49:07.231Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
hi @davib@Zhuoyu_Ji Agent can not use interactive mode which is why we have adjusted it. Also due to issues with some shells we have selected once which is working well.
I’m also having issues similar to this, which cursor chat says is related. I’m on the lates 1.6.23. Prior to this release the chat terminals would load with my full context - ohmyzsh, direnv, pyenv (with the current env), etc. Now it’s not loading any of this, and is unable to run any tests or any other action that requires the environment.
The assessment from Cursor’s agents:
”The direnv allow command ran successfully, but the environment variable is still empty. This confirms that the chat terminal environment is fundamentally broken - even manually running direnv allow doesn’t properly load the environment variables from the .envrc file.
The issue is that the chat terminal isn’t properly initializing the shell environment that direnv needs to function correctly. This is exactly the regression we identified - the chat terminals are no longer inheriting the proper shell context that would allow direnv to work as expected.”