Skip to guide

Use onemind with Cursor

Cursor supports a CLI-selected Team Project target and an independently activated ordinary Project repository target. The Project instruction destination is .cursor/rules/one-mind.mdc. Native BETA sync separately maintains a stable user-wide bootstrap rule in ~/.cursor/plugins/local/onemind-team-context/rules/one-mind.mdc; it does not copy Project content into that global rule. Cursor has no skills capability via onemind.

macOS app

  1. Sign in to OneMind BETA.app and connect Cursor from Team where the host supports verified Connect.
  2. Open Mind, choose the intended Project, and bind its exact folder on this Mac.
  3. Open the approved Mind, choose Sync, check the tool/device, and choose Sync now. Wait for confirmed delivery.
  4. Start a fresh Cursor chat or Agent session from that folder. See Mind Sync for pending, offline, and recovery states.

The native app manages its own connection and folder binding; CLI repository detection is a separate terminal workflow.

CLI

From the repository you open in Cursor, run:

onemind project cursor .

The CLI detects Cursor and prints a message asking you to open onemind and choose the Project Mind for the detected folder. Open the onemind app, find the detected folder in Sync Setup, and bind it to the intended Project Mind. Then run:

onemind sync
onemind status

Confirm that <repository>/.cursor/rules/one-mind.mdc contains the managed Project package. On the first write, onemind saves the previous file as a backup in the .one-mind folder. Start a fresh Cursor chat or Agent session.

The optional host integration at ~/.cursor/plugins/local/onemind has a separate lifecycle managed by onemind integrations. onemind atomically replaces its owned rule block, prevents version regression, and preserves the prior rule on validation failure. The bundled Cursor rules/skill/MCP package is managed atomically; explicit install/update/uninstall runs a read-only cursor-agent --print --output-format json marker probe when the executable is available. Only an exact fresh marker result is connected evidence; passive status never launches Cursor.

Cursor Project composition sync and Project structured-outbox sync are supported. For an activated Cursor Project binding, onemind can sync reviewed memory and, when upload is enabled for the target in Sync Setup, upload that Project's structured onemind proposal queue. It never reads Cursor's proprietary chat database or treats arbitrary file changes as durable knowledge.