You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/integrations/cursor.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,7 @@ When per-user mode is on, members who haven't connected their account will see a
87
87
3. Read the confirmation dialog - it explains what changes for your workspace - and confirm.
88
88
89
89
What happens when you switch:
90
+
90
91
- Members must connect their own Cursor API key from the **Connections** page before they can use `@cursor`.
91
92
- PRs will be opened on each user's behalf instead of by the Cursor bot.
92
93
- Cursor usage is tracked against each member's individual plan.
@@ -100,6 +101,7 @@ What happens when you switch:
100
101
3. Confirm in the dialog.
101
102
102
103
What happens when you switch back:
104
+
103
105
- All `@cursor` tasks will be created by the shared Cursor bot, regardless of who triggered them.
104
106
- Usage is billed to the workspace account.
105
107
- Members' personal connections are retained but ignored until per-user mode is re-enabled.
@@ -174,6 +176,7 @@ If you don't specify a repository and the project has multiple mappings, Cursor
174
176
Whether you're using the assignee or a comment, Cursor uses the work item's title and description as context. The clearer and more specific your work item (and comment), the better the result.
175
177
176
178
Include:
179
+
177
180
- What needs to change and where
178
181
- Any constraints or requirements (don't break this test, match this pattern, etc.)
179
-
- The acceptance criteria if it's not already in the work item description
182
+
- The acceptance criteria if it's not already in the work item description
0 commit comments