Feature request for product/service
Background Agent (GitHub, Slack, Linear,…)
Describe the request
Summary
The Cursor Agent window recently gained a Home option that lets you start an agent without picking a specific repository, and it also supports Workspaces that group multiple repositories together. I’d love to have the same options when configuring Cursor Automations.
Current behavior
When creating a Cursor Automation, I have to pick a single repository. There is no equivalent of:
- Home — running an automation without binding it to one repo
- Workspace — running an automation across multiple repos that belong to the same product/team
Proposed behavior
Allow Cursor Automations to target:
- Home (no repo specified), mirroring the Agent window option.
- A Workspace containing multiple repositories.
Use case
Our team owns a product split across multiple repositories — frontend, backend, and several microservices. We want to wire Cursor Automations into a single team Slack channel so that anyone can say something like:
“Open a PR that adds a feature flag for X and exposes it in the settings screen.”
…and have the agent figure out which repos to touch.
Today this is awkward because:
- The requester (often a non-engineer — PM, designer, sales) has to know in advance which repo the change belongs to before triggering the automation.
- Changes that legitimately span multiple repos (e.g. a backend flag + a frontend toggle) can’t be expressed in a single automation run.
If Automations could target Home or a Workspace, the agent itself could decide which repo(s) to touch, and non-engineers could file requests without thinking about repo boundaries. This unlocks a much more agentic usage of Cursor for cross-functional teams.
Why it matters
- Lowers the barrier for non-engineers to use Cursor Automations.
- Matches the mental model already established by the Agent window.
- Better fit for microservice / polyrepo architectures.