When Agent Window is launched locally, the terminal and diff functions are available.
However, when trying to use them on the SSH connection target, they are available, but only for File or Chat.
Is it not yet supported on the SSH connection target?
Sometimes I want to do small tasks myself after letting the AI do the work, but is that not possible now?
Hey, this is a known limitation. Glass Agent Window doesn’t yet have full parity with local usage when connected via Remote SSH. Some tabs in the right panel like Terminal and Diff/Review don’t show up in remote workspaces.
We’re actively working on this and Remote SSH parity in Glass is on the roadmap, but I can’t share an exact ETA.
As a temporary workaround, use the regular Cursor window for Remote SSH, not Agent Window or the Glass layout. Terminal and diff work there like before.
@deanrie
Thank you. So that’s how it is, then.
@deanrie
By the way, if you want to use skills or MCP via SSH, you can only access files on the remote server, right?
Yeah, that’s right. When you’re connected via Remote SSH, the agent runs in the remote extension host, so it can see the remote machine’s file system.
Skills are loaded from .cursor/skills/ in the open workspace (on the server) and from ~/.cursor/skills/ in the remote user’s home directory. Local skills from your machine aren’t available in that session.
MCP works in a similar way: stdio servers from the workspace .cursor/mcp.json and the global ~/.cursor/mcp.json are started on the remote machine (commands run where the extension host runs). If you need a server that talks to local resources, you can run an HTTP or SSE MCP server locally and connect to it by URL. Then the transport doesn’t depend on where the extension host is running.
One small caveat: if the remote is a Windows host, there’s a known issue with loading skills over SSH. On a Linux target it usually works fine.
