Evidence record / cursor

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-cursor-grok-bot-terms-add-meeting-use-obligations-without-establishing-feature-availability

Grok Bot terms add meeting-use obligations without establishing feature availability. The separate Grok Bot computer-use product’s terms now cover listening, processing, capturing and transcribing meeting content. The customer must determine and obtain required notices and consents. This is contract text, not a universal rule about every meeting or proof the feature has shipped. The product remains bundled with paid individual Cursor plans and Teams; inspected docs retain allow-all networking without policy and Enterprise-only enforced review and Action Recording, off by default.

Channel: docs-only. Half: both. Date: 2026-10-12 terms; historically captured 2026-10-13.

Operator consequence: Decide meeting-use policy before allowing it. Availability and admin controls are unverified; require a feature release and control documentation to settle them. Keep Grok Bot policy separate from the agent CLI and IDE. Do not infer legal obligations beyond the terms’ required-notice and required-consent wording.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-cursor-grok-bot-terms-add-meeting-use-obligations-without-establishing-feature-availability

Profile citations

  • cursor / claim / grok-bot-meeting-terms

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact