1. Keep Lex boring and dependable.
Lex 4.4.1 preserves work continuity and bounded context across sessions. Continue improving recall relevance, precise recovery and inspectable handoffs, with local SQLite and shared PostgreSQL options.
Status checked • October 7, 2026
The roadmap is moving from tools to an operating stack.
Lex, AXF, LexSona and LexRunner have public source repositories and npm releases. AXF, LexSona and LexRunner are open source under Apache-2.0; Lex remains MIT. ContextForge has a tested local implementation and remains unpublished. LexThority is historical research with no active product commitment. Behavior and containment boundaries continue to evolve.
The near-term work is not another prompt pattern. It is the layer that lets agents remember, discover workspace capabilities, ask for authority, inherit behavior, and coordinate bounded work.
Current public surface
| Project | Status | Package | Source |
|---|---|---|---|
| Lex | Public MIT core for work continuity, bounded context, policy, recall, instructions, CLI, MCP, and API. | npm 4.4.1 | GitHub |
| Lex MCP | Public MCP wrapper for Lex surfaces. | npm 4.4.1 | NPM package |
| AXF | Public Apache-2.0 framework for workspace capability contracts. | npm 2.1.3 | GitHub |
| ContextForge | Ratified pure context linker; first local implementation tested on explicit inputs. | Private local 0.1.0; no public source or npm release. | Implementation status / Public decision |
| LexThority | Historical authority research; no active product commitment. | No npm release. | GitHub |
| LexSona | Public Apache-2.0 behavioral constraint engine. | npm 2.0.4 | GitHub |
| LexRunner | Public Apache-2.0 integration plans, gates, receipts and assisted Attempt coordination. General headless supervision remains unproven. | npm 2.4.0 | GitHub |
Near-term roadmap
2. Make AXF the workspace capability layer.
AXF should make local repo know-how discoverable and runnable without turning every capability into raw shell improvisation. Expect more adapter examples and lifecycle hardening.
3. Prepare ContextForge for public use.
Ownership and input contracts are ratified, and the first local implementation is tested. Public release, richer context adapters and a LexRunner consumer remain downstream work. Authentication and effect authorization remain independent.
4. Separate LexSona behavior from LexRunner flow.
LexSona should return deterministic behavioral constraints. LexRunner should consume those constraints, not become the persona engine.
5. Extend LexRunner’s assisted coordination.
The assisted Attempt lifecycle is implemented. Public headless launch, host/reboot recovery evidence and Stage 5 fault-injection remain open. Keep execution roots, observed effects, verification and merge authority explicit.
6. Prove the stack outside development.
Analyst, product, support, security, and operations workflows should use the same surfaces: memory, capability, authority, behavior, flow, and receipts.
Design principles
Use existing brokers
The stack should cooperate with OAuth, cloud IAM, GitHub permissions, and enterprise security tooling. It should not invent a shadow identity provider.
Fail with operator-ready detail
When a credential, policy, or tool blocks work, the agent should be able to tell an operator what was attempted, what failed, and what permission or action is needed.
Preserve agent autonomy
The goal is bounded agency, not bureaucracy. Agents should reason freely inside a workspace while effects are gated, receipted, and recoverable.