At the moment, I run cursor on my worker machine using the remote ssh extension. Unfortunately, if the wifi goes down or I close my computer the agent stops working because the ssh connection dies. My goal is to allow the worker to continue running even if the UI disconnects. Then when the UI reconnects it catches up.
Links:
Hi @sshleifer – for short disconnects (<5 mins), it should be able to auto-reconnect without making you reload the editor. However, for long reconnects, you will have to reload the window, since the remote server will automatically shutdown after 5 minutes of no connected clients. For long running commands, I would recommend that you continue to use tmux for that.
Yeah I think the ask here is that the agent daemonizes and runs outside of the VSCode extension host. Sort like remote agents, but not on AWS. In the SCM/build/ test environment I work in, AWS is not an option.
Hi @sthaber1 , for this, I’d recommend you try using the Cursor CLI in a tmux session, or try background agents.
Hi! I do currently use CLI for this use case, but it’s missing some of the functionality that makes Cursor GUI great. I like being able to apply/reject changes graphically, line-by-line. I like that the GUI intelligently includes rules files that are not marked as “always include”. (The CLI doesn’t seem to do this, but maybe it’s on the roadmap.) I find that the semantic search that index offers works a lot better than the context-filling greps that the CLI does. Maybe index will come to the CLI someday too.