Your team's past sessions, in Claude Code's context on every turn.

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.
• Claude Code, and Node.js for the glen CLI.

Install Glen for Claude Code

1. 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

2. 02
   Install the plugin. This also adds Glen's status line to your Claude Code settings, unless you already have one. glen install also adds a login-shell check to your shell profile, git hooks when you run it inside a repository and, on macOS, a menu bar indicator showing your recording mode.

   bash

   glen install --agent claude

   To install only the plugin by hand instead, use Claude Code's own commands:

   bash

   claude plugin marketplace add Glen-Web-App/glen-claude-code-plugin
   claude plugin install glen@glen

3. 03
   Start a new session. If something looks wrong, glen doctor checks the setup, or ask the agent to "set up glen" and it fixes what doctor reports.

How it works

Try asking

• Why does the reminder job retry only once? Check glen before you change it.
• Has anyone on the team already traced this flaky auth test?
• Trace src/billing/invoice.ts:40-60 back to the conversation that wrote it.
• Use our release skill for this change.

Tools

The Claude Code 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, plus the previous reply for continuity.
• The finished turn: the agent's text, thinking, tool calls and tool results. Tool results can include file contents and command output.
• Workspace context: working directory, repository name, branch, commit and remote URL.
• The agent name (claude-code), a session id, the permission mode and how the session started.
• After a git commit: the commit hash, remote URL, branch and session id.
• Glen masks the secrets it detects before storing a turn. Detection can miss some, so don't rely on it to protect a secret that ends up in a session.
• 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