GLEN FOR CODEX

Codex turns that begin with what your team already worked out.

The glen plugin connects Codex to your organization's shared memory. Before each turn it adds the memories that match your prompt to the context; after each turn it records your prompt and Codex's final reply, next to sessions from Claude Code, Cursor and the rest of the team.

Install Glen for Codex 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.
Codex, and Node.js for the glen CLI.

Install Glen for Codex

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
Install the plugin. This runs Codex's plugin commands, writes glen's hooks to ~/.codex/hooks.json and trusts them in ~/.codex/config.toml. 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 codex
```
03
Start a new session. If turns aren't recorded, run glen doctor. If it reports untrusted hooks, open Codex, run /hooks and trust the glen hooks.

How it works

SessionStart

Adds your organization and recording mode to the context, shows a notice when Glen is off, incognito or silent, and runs glen doctor --auto in the background.

UserPromptSubmit

Sends your prompt, the previous reply and workspace context to Glen, gets back the memories that match, and adds them to the context for that turn.

Stop

Records the finished turn's final reply.

PostToolUse (Bash)

After a git commit, links the commit to the session. When a command prints a pull request for this repository, the agent offers Glen's local reviewer, once per pull request.

Why the hooks live in ~/.codex/hooks.json

Codex doesn't yet run hooks declared in a plugin manifest, so glen install writes them to the user config layer and leaves other tools' hooks in that file alone. Re-running it repairs the registration. Codex skips untrusted hooks without saying so, which is why the install also records trust.

It never blocks Codex

Every hook exits 0, so a Glen outage can't stop a Codex session.

Try asking

Before you touch the rate limiter, what did the team decide last time?
Who worked on the webhook retries, and what went wrong?
Trace this function back to the conversation that wrote it.
That memory about Friday deploys is out of date. Forget it.

Tools

The Codex 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 (codex) 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.

Remove it

glen uninstall removes the plugin, its hooks and the rest of glen's local setup.

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.