Public MIT core • npm 4.4.1

Lex gives agents repo-local memory and policy context.

Lex preserves decisions, blockers and next steps as structured work snapshots, then recalls relevant context for the next session. Bounded context bootstraps help an agent continue the work.

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

npm package GitHub Quick start

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 is	Memory, policy context, local storage, and stable contracts for agents.
Lex is not	A runner, an IAM broker, a credential store, or a hosted memory service.
Pairs with	AXF for workspace capabilities, LexSona for behavior, and LexRunner for orchestration. ContextForge is a context-linking library with a tested, unpublished local implementation; effect authorization stays separate.