=)Where does the bug appear (feature/product)?
Editor, Tab & Chat (autocomplete, Composer, in-editor agent)
=)Describe the Bug
It explicitly states that it cannot establish an SSH connection (Composer).
=)Steps to Reproduce
1-You might want to ask for some files to be deployed to the live environment.
2-You can ask them to establish an SSH connection.
=)Expected Behavior
Just as I have done before, it should upload the relevant files to my server—either by using a file already registered in the project or by utilizing the SSH credentials I provide in the chat.
=)Operating System
Windows 11
=)Version Information
Version 3.29.9
=)For AI issues: which model did you use?
Composer 2.5(Fast)
=)Additional Information
This is a prompt I use constantly. I frequently issue commands like “deploy changes to production.” Previously, if the active session had access to my SSH credentials, it would execute the task and then warn me (e.g., “You’ve shared your credentials here; please change them”). Now, however, it simply refuses—or claims it’s unable—to perform such actions. I haven’t seen any official announcement regarding a change like this. If this is the new normal, I’ll definitely consider canceling my subscription; this feature was what made my workflow so much faster. Without it, Cursor is essentially useless to me. Also, when I started experiencing this issue, I noticed—and I hope this isn’t misunderstood—that it became a bit… foolish. Or perhaps I just became extremely annoyed. I’m not sure.
=)Does this stop you from using Cursor?
No - Cursor works, but with this issue(i don’t use now for that thing)
For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)
For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…
Additional Information
Add any other context about the problem here.
Does this stop you from using Cursor?
Yes - Cursor is unusable
Sometimes - I can sometimes use Cursor
No - Cursor works, but with this issue
The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!
Should it be considered a bug that it rejects me outright without providing any error message? I mean, just yesterday—and I know I shouldn’t have shared my SSH credentials in the chat—it was able to do it, but today it just says, “I can’t do that for you”
Hi @where_was_i, this isn’t something applied to your account. It’s almost certainly the Auto-Review run mode. Auto-Review checks each command before the agent runs it on its own, and it holds back ssh, scp or rsync commands that send files to (or run scripts on) a remote server unless that server was clearly part of your request. When it does, Cursor should show an approval card you can accept.
If you’d rather not approve these one by one, either of these works:
Open Cursor Settings → Agents → Execution and Approvals.
Under Allowlist Options, add ssh, scp and rsync to the Command Allowlist. Allowlisted commands run without the review.
Or set Run Mode to Allowlist or Run Everything for this project. Keep in mind that either way the agent can then reach those servers without asking.
If that doesn’t match what you’re seeing, could you post a screenshot of the exact message you get when the command is rejected?
Thanks @where_was_i, that screenshot settles it. Since you’re on Run Everything, Auto-Review isn’t involved, so you can ignore my earlier suggestion. In that request the agent never tried to run ssh at all: Composer declined on its own and answered with text. Nothing in Cursor blocked the command, and nothing changed on your account.
Models are often unwilling to log in to a server with a password pasted into chat. A setup that doesn’t need that works much more reliably:
Set up SSH key login for your server and add it to ~/.ssh/config with a short host name (for example Host prod).
Add a deploy script to the project (deploy.ps1 or deploy.sh) that uses scp or rsync to prod.
In a new chat, ask the agent to “run the deploy script”.
If Composer still declines, try the same request with a different model from the model picker, and let me know if that one refuses too.
Since the server password was shared in chat earlier, it’s worth changing it.
I successfully performed an update by adding an SSH key, which resolves the issue I was experiencing. Naturally, I would always change the server password after sharing it in the chat—which was the very reason I brought this topic up for discussion in the first place. Did Composer download some sort of “silent” update? Given that Cursor is less widely used compared to other developer-focused AI agents, isn’t this—requiring users to manually add an SSH key and provide system details—a rather poor design choice if the goal is to appeal to a broader user base? By the way, we can certainly continue this discussion further! Best regards.
