Skip to content

cursor-integrations-setup.md

Latest commit

 

History

History
63 lines (44 loc) · 2.57 KB

cursor-integrations-setup.md

File metadata and controls

63 lines (44 loc) · 2.57 KB
Raw

Cursor Integrations Setup

Complete these steps after the Slack workspace is ready. Cursor Automations require all three integrations.

1. Connect Slack

  1. Open cursor.com/dashboard → Integrations
  2. Find Slack → Connect
  3. Authorize the Paradise Planner HQ workspace you created
  4. Confirm the Cursor app is installed in Slack (Apps section)

Verify: In Cursor → Automations → create a test automation → Slack trigger → you should see #vacation-hq and the other channels.

2. Connect GitHub

  1. Same dashboard → Integrations → GitHub → Connect
  2. Grant access to repository: ether314/Vacation
  3. Confirm default branch is main

Verify: In an automation draft, git scope should list ether314/Vacation.

3. Enable Cloud Agents

  1. Dashboard → Cloud Agents (or Agents tab)
  2. Enable cloud compute for automations that modify code
  3. Ensure your plan includes cloud agent minutes

Verify: When saving a Slack-triggered automation with repo checkout, no "cloud compute required" blocker appears.

4. Import the agent swarm automations

Prefill definitions live in docs/automations/.

For each JSON file in that folder:

  1. Open Cursor → Automations → New automation
  2. Ask your Cursor agent to open the prefill: "Open automation from docs/automations/<name>.json" — or copy fields manually from the JSON
  3. Select the matching Slack channel in the trigger (channel IDs are workspace-specific)
  4. Confirm repo ether314/Vacation / branch main
  5. Save and enable the automation
File Channel to select
chief-of-staff.json #vacation-hq
product-agent.json #vacation-product
engineering-agent.json #vacation-engineering
qa-agent.json #vacation-qa
deploy-agent.json #vacation-deploy
ops-agent.json #vacation-ops
pr-review-bot.json (git trigger — pick #vacation-engineering for Slack posts)

Release policy: All code-changing automations follow AGENTS.md — automatic commit, push main, build-web.ps1, and Firebase deploy after every shippable change. Agents must never ask permission or skip deploy.

5. Verification checklist

  • Slack connected; all 6 channels visible in Automations UI
  • GitHub connected; ether314/Vacation accessible
  • Cloud Agents enabled
  • All 7 automations saved and enabled
  • Test message in #vacation-hq triggers Chief of Staff agent

Next step: bootstrap-test.md