Work with us
AI tools / Developer and coding AI / Cursor

How to govern Cursor

An AI code editor that edits files and runs commands across a codebase, often without a review of each step.

Anysphere · Certrak checks Cursor every quarter, and sooner when Anysphere ships a capability change or a customer declares a new use of it · Last checked 16 Oct 2026 · Next check by 16 Jan 2027

Guidance updated Reviewed the changelog from 1 September to 13 October. Projects adds a cloud coordinator agent that plans work, runs many sub-agents, keeps shared memory across machines and can act on Slack, schedule or pull-request events without being prompted. Agent execution can run on self-hosted machines with computer use, mobile remote control of local agents is on by default outside Enterprise, and an app marketplace grants third-party apps write access to checks and reviews. Full changelog ↓

How Cursor is used

We see two common ways businesses use Cursor, and we govern each one on its own terms. If your team uses it differently, that is fine: you describe the use in your own words and Certrak works out the governance from what it actually does.

Code generation and review

Consequence to people: Medium

Writing or reviewing code, with a developer in the loop

Internal informationEvery output reviewedInternal use onlyRuns code or scriptsActs on its own
  • Review rhythm: Monthly check-in
  • Governance is mostly about: Safe everyday use; A person stays accountable; What it may be given

Autonomous coding agent

Consequence to people: Medium

Code AI operating in agent mode - taking actions across repositories, running commands, deploying

Internal informationMost outputs reviewedInternal use onlyRuns code or scriptsActs on its own
  • Review rhythm: Monthly check-in
  • Governance is mostly about: Safe everyday use; A person stays accountable; What it may be given

Governing Cursor in practice

  1. Name one person who owns Cursor in your business. Governance starts with a name.
  2. Write down what Cursor is used for. Certrak recognises 2 common uses: Code generation and review and Autonomous coding agent. Yours may differ; write down yours.
  3. Decide what Cursor may and may not be given. Internal business information is in scope, so name what stays out.
  4. A person reviews most outputs and exceptions are flagged. Agree what counts as an exception and who sees it.
  5. Cursor can run code or scripts without a person approving. Record which of these you allow, and who can change that.
  6. Look again at each use on the rhythm shown against it, and sooner on any of these: industry incidents, vendor model updates and autonomy level changes.

What changed, and how Certrak responded

We record every check here, including the ones that changed nothing. A check that found no governance change proves we looked.

  1. Guidance updated Scheduled review

    Cursor Projects

    Anysphere shipped it 10 Sep 2026.

    Reviewed the changelog from 1 September to 13 October. Projects adds a cloud coordinator agent that plans work, runs many sub-agents, keeps shared memory across machines and can act on Slack, schedule or pull-request events without being prompted. Agent execution can run on self-hosted machines with computer use, mobile remote control of local agents is on by default outside Enterprise, and an app marketplace grants third-party apps write access to checks and reviews.

    How Certrak responded: Where Cursor is used for ordinary code assistance, it can now run code and act on events without a person starting each task. Owners are asked whether their people use Projects or event-driven agents; if they do, the system is treated as running code on its own and the matching controls apply.

    Vendor release note →