Integration proposal: Cursor 3 marketplace submission + parallel-agents update (auto-drafted 2026-06-29)

[NativeTeachingAidsB]

Score: 12 — Cursor 3 shipped a plugin marketplace April 2, 2026; codetalker should be listed. Labels to add manually: integration-proposal, auto-generated, urgent.

Auto-generated by the weekly-landscape-scan routine. Draft spec in docs/superpowers/specs/2026-06-29-integrate-cursor3-marketplace.md (on branch docs/landscape-report-2026-06-29). Do not promote to approved without human review.

What changed

Cursor 3 "Glass" (April 2, 2026) added:

• Agents Window: parallel agent execution across local/cloud/SSH
• Plugin Marketplace: 30+ launch plugins (Atlassian, Datadog, GitLab, Figma…). A plugin bundles MCP config + skills + hooks into one installable package.

docs/integrations/cursor.md predates Cursor 3 and doesn't cover the marketplace install path or parallel-agent narration behavior.

What this spec proposes

1. Submit codetalker to Cursor Marketplace as a plugin (one-click install vs. manual .cursor/mcp.json).
2. Update docs/integrations/cursor.md for Cursor 3.
3. Document behavior when multiple parallel agents call tts_speak simultaneously.

Key open questions

• Is the Cursor Marketplace open to third-party submissions, or invite/partner only?
• Exact hook event names in Cursor 3 plugin system (AgentStop? — needs verification from github.com/cursor/plugins).
• Daemon behavior with 3 simultaneous tts_speak calls — queue or overlap?

Effort

Medium — 3–5 days (plugin manifest + marketplace submission + docs update). If Cursor requires partnership for listing, timeline extends.

---

Routine run: 2026-06-29 | Landscape report: docs/landscape-reports/2026-06-29.md