Guide • Lex npm latest • AXF npm latest

Start with memory, then add capabilities.

The public path is simple: install Lex for repo-local memory and policy context. Add AXF when the agent needs reliable workspace actions. Follow LexThority as authority decisions become a first-class layer.

Install

Lex CLI

npm install -g @smartergpt/lex lex init --yes lex doctor

Lex MCP

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

AXF

npm install -g @smartergpt/axf axf doctor axf list

Working loop

1. Initialize Lex in the workspace.

Let Lex create the local structure it needs, then keep its files in the repo when the memory and policy should travel with the project.

2. Capture real work state.

Use Frames for meaningful checkpoints: what changed, what is blocked, what module is involved, and what the next agent should do.

3. Add policy only where it pays rent.

A small lexmap.policy.json is better than a giant aspirational one. Start with module ownership, forbidden edges, and known risk boundaries.

4. Promote repeated work into AXF.

If agents keep rediscovering the same build, test, search, or diagnostic command, make it an inspectable AXF capability.

5. Route authority questions explicitly.

For actions with side effects, start modeling the effect and envelope. LexThority is the preview surface for that decision layer.

AXF

Workspace-owned capabilities and adapter contracts.

Project page

LexThority

Authority envelopes and effect receipts.

Preview page