Cursor

FreeRide works in Cursor's agent. In a repo that's set up, the agent gets a briefing on the project, logs what it builds and keeps the docs up to date.

Install

FreeRide isn't in Cursor's Marketplace yet, so it installs from GitHub into Cursor's local plugins folder. Open Terminal and run:

git clone https://github.com/freeride-dev/freeride ~/.cursor/plugins/local/freeride

Then restart Cursor. It only loads plugins at startup.

On Cursor's company plans, an admin may need to allow local plugins first.

Open Customize, find FreeRide and select Authenticate next to the freeride server. A browser window opens: sign in (Google or email) and approve.

Set up a repo

Once per repo. Open the repo in Cursor and, in Agent mode, type:

/freeride-setup

Or just ask: "Set up FreeRide for this project." If you forget, the agent offers once, the first time you mention the project or it logs work there.

Setup asks which project the repo belongs to, or creates a new one. It writes .freeride.json (the project's id, no secrets) and adds FreeRide's rules to AGENTS.md (read by Codex and Cursor) and CLAUDE.md (read by Claude Code), including a line that names the project, because Cursor can't tell FreeRide which repo it's in. It shows every change and asks once. Commit the files, and teammates who pull the repo are set up too.

Using it in Cursor

Use Agent mode. Ask mode is read-only, so Cursor blocks FreeRide's tools there.
Tool approvals. Cursor asks before each tool call. You can let FreeRide's tools run without asking.
Reminders. FreeRide's nudges work in Cursor too. Two come a step later than in Claude Code: the "FreeRide is connected" reminder right after the first edit instead of before it, and the reminder after compaction at the agent's next tool call.

Updates

The plugin checks for updates once a day on its own. If you installed it before October 17, 2026, run this once to get the version that does:

git -C ~/.cursor/plugins/local/freeride pull

If something's off