Slack, GitHub, Linear, Jira and Workflow Integrations

Done means you can choose the integration that matches the source of work.

Connect Cursor only to the external systems the workflow actually needs, with approvals around access.

Use Integrations when Cursor work should start from an issue, PR, alert or team conversation. Keep the boundary narrow.

Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.

Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.

Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.

1. 1Identify the system where the work originates.
2. 2Choose the integration surface that preserves context.
3. 3Define what the agent should do and when it should do nothing.
4. 4Confirm identity, permissions and notification behavior.

The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.

Verification decides the next move.

Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.