Components

This directory contains runtime components built on top of the LightMem2 framework. Each component can expose one or more host adapters without duplicating its shared runtime logic.

The current public repository ships one component:

Component	Status	Role	Docs
TokenPilot	public	Runtime component for context stabilization, reduction, and lifecycle-aware eviction	components/tokenpilot/README.md

Component And Adapter Split

LightMem2 separates:

• component packages
  • reusable runtime logic
  • state and policy layers
  • host-agnostic contracts
• host adapters
  • installation and bootstrap
  • transcript/session bridging
  • host-specific command and hook surfaces

This layout is meant to let a single component support multiple agent hosts over time.

How To Read This Directory

Use the root README.md first if you want the fastest path to:

• install the repo
• install the current component
• verify the runtime path in a real session

Use a component subtree when you need component-specific material such as:

• command surface
• package layout
• configuration details
• runtime state layout
• debugging notes
• benchmark-specific experiment docs

Current Layout

components/
└── tokenpilot/
    ├── adapters/
    │   ├── openclaw/
    │   ├── codex/
    │   └── claude-code/
    ├── README.md
    ├── products/
    └── packages/
        ├── host-adapter/
        ├── product-surface/
        ├── runtime-core/
        ├── kernel/
        └── layers/

Naming Boundary

At the repository level, the framework name is LightMem2.

At the current runtime-compatibility layer, the shipped component still uses the established tokenpilot namespace for plugin id and persisted state. On OpenClaw, the current public session model prefix is lightmem2/<model>, while Codex CLI and Claude Code use the standalone lightmem2 <host> ... command surface. That boundary is intentional for now so the repo can move toward a multi-component layout without breaking the current working paths.