Feature request for product/service Background Agent (GitHub, Slack, Linear,…) Describe the request Cloud Agent Automations are useful for recurring or event-driven work, but some workflows need to run on the developer’s own laptop. Please add Local Automations: the same scheduling and trigger UX as Cloud Automations, but executed by the Cursor app harness on the local machine. Proposed behavior: Let users create automations that run against the current local workspace or a selected local repo. Execute through the Cursor app/agent harness so they can use the same local tools the agent can already use: shell, file system, git, browser, and configured MCP servers. Support manual, scheduled, and event-based triggers, such as repo changes, reminders, CI/check polling, PR/comment checks, or local time triggers. Show runs, logs, approvals, permissions, and history inside Cursor, with clear controls to pause, retry, or stop. Reuse existing local permission and approval boundaries so local automations cannot silently perform sensitive actions. Make runtime selection explicit: Cloud Automation for hosted always-on work, Local Automation for workflows that need the user’s laptop. Why this matters: Many automations depend on private local credentials, VPN-only resources, local MCP servers, or tools that are not available in a cloud sandbox. Some teams cannot send source code, environment state, or credentials to a remote automation environment. Local execution would make it possible to automate tasks like watching a PR, babysitting tests, checking internal dashboards, running local scripts, triaging logs via MCP, or doing workspace maintenance while keeping everything on the laptop. This would complement Cloud Automations rather than replace them: cloud for always-on hosted workflows, local for workflows that need the user’s machine, local network, credentials, and Cursor app context. Operating System (if it applies) MacOS

This is a cool feature, didn’t know about it. The only drawback is that it sees only cloud-configured MCP servers, not local ones.

Indeed, let us know how we can improve it further!

This is a reasonable workaround for coding tasks, but far from ideal especially for less technical folks wanting to setup simple local-only automations or recurring tasks. Tasks like Summarize my meetings and Slack conversations, etc. The specific use-case I’d like to enable for people on our team is automated maintenance of their local-only LLM Wiki / Second Brain style workspaces. These typically won’t have git repositories associated with them, so the Cloud Agents / My Machines workaround doesn’t really fit.

Support Local Automations in Cursor

Ideas Feature Requests

Tom_Coustols (Tom Coustols) June 9, 2026, 2:16am 4

hey man, you should give a curious eye to My Machines | Cursor Docs this is the solution you need

Automations - Connect via SSH

Topic		Replies	Views
Local routines / automations for Cursor Feature Requests cloud-agents , automations	6	644	July 2, 2026
Please allow local agents to manage and update automations and cloud agent environments Feature Requests cloud-agents , automations	1	62	August 17, 2026
Automations as Code or API Feature Requests cloud-agents , automations	13	394	August 14, 2026
Introducing Cursor Automations Release Discussions mcp , cloud-agents , github , long-running-agents , automations	23	6112	March 20, 2026
Cursor Automations: support "Home" and multi-repo Workspaces (parity with the Agent window) Feature Requests slack , automations , agents-window	4	264	May 23, 2026

Support Local Automations in Cursor

Related topics