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