How is Glen different from Roo Code's task context?

Roo Code's context keeps the current task coherent and resets when the task ends. Glen is durable, org-shared long-term memory that persists across tasks and is read and written by every agent and teammate in your organization.

How do I add Glen to Roo Code?

Glen is a standard MCP server. Add it to Roo Code's MCP server configuration, authenticate over OAuth or an API key, and the agent can call it to retrieve context and record observations in one round trip.

Shared memory for Roo Code

Roo Code is an autonomous coding agent that lives in your editor, reading and writing files, running commands, and working through multi-step tasks across your codebase with switchable modes for architecting, coding, and debugging. It keeps the current task's context coherent and supports MCP servers so you can extend what it can reach. What it does not have is a memory that persists between tasks and is shared with the rest of your team's agents: every new task starts fresh, rediscovering conventions, past decisions, and the shape of your system. Glen, shared memory for AI agents, gives Roo Code a durable, org-shared memory as a single MCP tool that retrieves long-term context and records new facts in one round trip.

Add Glen to Roo Code's MCP configuration and the agent gains one tool that both reads relevant long-term context and writes new observations. At the start of a task, Roo Code can pull what your team already knows, the architectural decision behind a module, the reason a workaround exists, the convention for a subsystem, so it stops relearning your codebase every session. As it finishes, it records the durable facts it discovered so the next task, in any editor, benefits. You avoid pasting the same context into the chat repeatedly and you avoid maintaining a scratchpad file that drifts out of date.

Roo Code's task context is scoped to the current run; it does not carry forward and it is not shared with your teammates' agents. Glen is org-scoped, so the memory spans every Roo Code session, every developer on your team, and every other agent your organization uses, in any framework. One developer's Roo Code session records a durable fact and another developer's session, or a CI agent, or a code-review bot, reads it next time. Because Glen is a standard MCP server, the memory Roo Code writes is equally readable from Claude Code, Cursor, Cline, or any MCP client, so the whole team's coding agents draw on one shared understanding of the codebase. Configure it once over OAuth or an API key and let the project knowledge compound.

FAQ

How is Glen different from Roo Code's task context?: Roo Code's context keeps the current task coherent and resets when the task ends. Glen is durable, org-shared long-term memory that persists across tasks and is read and written by every agent and teammate in your organization.
How do I add Glen to Roo Code?: Glen is a standard MCP server. Add it to Roo Code's MCP server configuration, authenticate over OAuth or an API key, and the agent can call it to retrieve context and record observations in one round trip.