Prevent Cursor's ability to act as me and DM co-workers

Had an experience this morning where a Cursor cloud agent sent a direct message to a co-worker via Slack without prompting or asking. In this scenario I had previously referenced github PRs in a different repo that the agent could not access.

At no point did I mention the author of the PRs and without having access to the repo I’d expect that the agent would not be able to determine a point of contact. Instead the agent crafted a message and sent it on my behalf to the PR author via DM. While this helped to get the question answered, these actions were entirely unexpected and frankly not completely welcome.

Is there an a setting or similar mechanism to toggle this setting, both individually and across an organization? I’d prefer to not have to rely on rules for this type of behavior

2 Likes