GLEN FOR CURSOR

Cursor sessions that start from what your team already knows.

The glen plugin records every Cursor agent turn into your organization's shared memory, alongside sessions from Claude Code, Codex and the rest of the team. When the conversation turns to past work, the agent runs glen search and gets an answer with citations instead of rediscovering it.

Install Glen for Cursor Open the Glen dashboard

What you need

A Glen account. Sign in at app.tryglen.com, or use Start free at the top of this page to create one. Search, skills and artifacts all work on the Free plan.
Cursor with agent hooks, and Node.js for the glen CLI.

Install Glen for Cursor

01
Install the glen CLI and sign in. Your active organization is saved locally; switch with glen org switch.
bash
```
npm install -g @tryglen/cli
glen login
```
02
In Cursor's agent chat, type /add-plugin and add the plugin (or install Glen from the Cursor marketplace once it's listed):
```
https://github.com/Glen-Web-App/glen-cursor-plugin
```
03
Start a new agent chat. The first message shows Glen's status line with your organization and recording mode. glen doctor checks the setup if it doesn't appear.

How it works

sessionStart

Shows Glen's status line (organization, recording mode) and reminds the agent it can search team memory. No memory is injected here.

beforeSubmitPrompt

Records your prompt with its workspace context before the turn runs.

afterAgentResponse

Records the finished turn: your prompt and the agent's reply.

afterShellExecution

After a git commit, links the commit to the session, so code can be traced back to the conversation that wrote it.

Recall is on demand

Cursor's hooks can't add context to every turn, so the agent recalls by running glen search in the shell. The bundled rule and the search skill tell it when to.

Try asking

Why is the checkout retry cap 3? Check glen before you change it.
Has anyone on the team already debugged this webhook timeout?
Use our add-feature-flag skill for this change.

Tools

The Cursor plugin reaches Glen through the glen CLI and its hooks, not through MCP tools. The same server also runs a remote MCP endpoint for chat clients and any other MCP client; the MCP server reference covers it.

What Glen sends and stores

The prompt you send and the agent's final reply for each turn.
Workspace context: repository name, branch, commit and remote URL.
The agent name (cursor) and a session id, so turns from one session stay together.
Content-free error codes about the glen CLI itself (command, flag names, versions). Turn them off with glen telemetry disable.

Everything goes to your organization in Glen and nowhere else. Retention, deletion and the services Glen uses are in the privacy policy and the list of sub-processors.

Turning it off

Go off the record

glen incognito keeps recall working and writes nothing to team memory. Admin analytics still count your prompts, as numbers only.

Turn Glen off

glen off recalls nothing and records nothing. glen on turns it back on. Both apply on every machine and agent.

Forget something

Ask the agent to forget a wrong or outdated memory (the forget skill), or remove it from Memories in the dashboard.

Privacy and support

What Glen stores, how long it keeps it and how to have it deleted are covered in the Glen privacy policy. For anything the policy doesn't answer, write to support@tryglen.com. Stuck on setup? The support page says what to include.