Plugins
The current LightRSI architecture separates reusable feature packages, presets, host adapters, and user-facing products. The word plugin also appears in host installation commands, where it refers to a host's native integration mechanism.
Packages, Presets, and Products
These layers have different responsibilities:
| Layer | Description |
|---|---|
| Shared packages | Foundation infrastructure and composable features such as stabilization, reduction, and eviction |
| Presets | Verified feature combinations, including TokenPilot |
| Host adapters | Host discovery, installation, runtime hooks, and product registration |
| Products | User-facing workflows and surfaces, including Context Cleaner, the shared CLI, and MCP interfaces |
TokenPilot and Context Cleaner
| Name | Type | Role |
|---|---|---|
| TokenPilot | Preset | Composes cache-aware context-management policies |
| Context Cleaner | Product | Presents tasks and recommendations, takes explicit approval, and reports cleanup status |
Cleaner reuses shared task lifecycle and host rewrite capabilities. Its public workflow is available on OpenClaw, Codex, Claude Code, and DeepSeek Harness; it is not integrated in the pi and OpenCode adapters yet. DeepSeek Harness provides native /tokenpilot-clean commands; it is not registered in the shared CLI.
Native Host Plugins
TokenPilot integrates with OpenClaw, Codex, Claude Code, DeepSeek Harness, pi, and OpenCode. OpenClaw uses a native plugin slot; Harness uses a native Cordis plugin for optional context eviction and session status. Codex uses a local proxy and hooks, while Claude Code uses a local gateway and MCP. pi and OpenCode run in-process, with no proxy or gateway.
These integration mechanisms do not make every product or feature available on every host. See Host Compatibility for the supported combinations.
Next
- Plugin Lifecycle — the state machine
- TokenPilot Overview — explore the preset
- Context Cleaner — use the cleanup product
- Build Your First Plugin — start developing