Public MIT core • npm latest

Lex gives agents repo-local memory and policy context.

Lex stores structured work snapshots, recalls relevant prior context, and connects that context to repository policy when a policy file is available.

It is the public foundation of the stack: durable Frames, Atlas neighborhoods, policy checks, local SQLite, CLI, MCP, and TypeScript APIs.

First useful test
Ask your coding agent:

"Review Lex in the context of this workspace.
What benefits would it provide here, if any,
and where would it not help?"

What Lex does

Frames

Durable work memory: reference point, summary, blockers, next action, branch, ticket, and module scope.

Recall

Prior context on demand, shaped for agent handoffs and everyday work continuity.

Atlas neighborhoods

Nearby module context around a recalled Frame, without flooding the model with an entire codebase.

Policy

Architecture boundaries as code: modules, ownership, allowed edges, forbidden edges, flags, and permissions.

Instructions

Canonical assistant guidance projected into host-specific files such as Copilot and Cursor instructions.

Agent surfaces

Scriptable CLI, MCP wrapper, structured JSON output, recoverable errors, and TypeScript APIs.

Install

CLI

npm install -g @smartergpt/lex lex init --yes lex remember --reference-point "handoff" --summary "..."

MCP

npm install -g @smartergpt/lex-mcp npx @smartergpt/lex-mcp

Project dependency

npm install @smartergpt/lex

Where it fits

Lex isMemory, policy context, local storage, and stable contracts for agents.
Lex is notA runner, an IAM broker, a credential store, or a hosted memory service.
Pairs withAXF for workspace capabilities, LexThority for authority decisions, LexSona for behavior, and LexRunner for orchestration.