Quick Start
Install
Run the install script at the root of your target repository.
Linux / macOS / Git Bash
curl -fsSL https://raw.githubusercontent.com/tower1229/LingXi/main/install/bash.sh | bashWindows PowerShell
irm https://raw.githubusercontent.com/tower1229/LingXi/main/install/powershell.ps1 | iexWhat Installation Adds
LingXi installs the currently supported product surface into your repository, including:
.agents/plugins/marketplace.json.codex-plugin/plugin.jsonskills/scripts/templates/
It also creates project-local runtime artifacts such as:
.lingxi/(host-agnostic core).codex/config.toml,.codex/hooks.json,.codex/agents/(Codex adapter).claude/settings.json,.claude/agents/,.claude/skills/(Claude Code adapter)AGENTS.md,CLAUDE.md(only when missing)
Runtime Layout
The current runtime layout looks roughly like this:
.lingxi/
tasks/
memory/
INDEX.md
project/
share/
state/
processed-sessions.json
distill-journal.jsonl
memory-ops.jsonl # created on demand
setup/
automation.session-distill.toml
.codex/
config.toml
hooks.json
agents/
lingxi-session-distill.toml
.claude/
settings.json
agents/
lingxi-session-distill.md
skills/
AGENTS.md
CLAUDE.mdThese areas are used for:
tasks/: task documentsmemory/: project and shared memory notesINDEX.md: the memory indexstate/: processed sessions, distill journal, and lazily-created memory ops logs.codex/config.toml: enables repo-local Codex hooks.codex/hooks.json: defines LingXi's repo-localUserPromptSubmithook (Codex).claude/settings.json: defines LingXi's repo-localUserPromptSubmithook (Claude Code).claude/agents/: Claude Code local agent config.claude/skills/: LingXi skills copied for Claude Codesetup/: generated automation artifacts.codex/agents/: Codex local agent config
Bootstrap
If you used the remote install script, bootstrap is usually already handled for you.
If you synced LingXi files manually, or want to rerun runtime and automation registration, run:
npm run lx:bootstrap
# or
node scripts/lx-bootstrap.mjsThis step:
- initializes
.lingxi/ - writes
AGENTS.md(only when missing) - creates or merges
.codex/config.toml,.codex/hooks.json(Codex adapter) - generates
.codex/agents/lingxi-session-distill.toml - creates or merges
.claude/settings.json(Claude Code adapter) - generates
.claude/agents/lingxi-session-distill.md, copies skills to.claude/skills/ - writes
CLAUDE.md(only when missing) - generates
.lingxi/setup/automation.session-distill.toml - registers the session-distill automation (Codex only)
You can use --host to generate artifacts for a specific host only:
node scripts/lingxi-setup.mjs --host codex # Codex only
node scripts/lingxi-setup.mjs --host claude # Claude Code only
node scripts/lingxi-setup.mjs --host all # both (default)Additional notes:
- For meaningful repository requests, LingXi injects the smallest relevant memory set automatically through a repo-local
UserPromptSubmithook (Codex or Claude Code). - On native Windows, setup still writes the hook config, but the current Codex runtime does not execute hooks natively yet.
First Use
The main foreground capabilities in LingXi are task and vet.
A good starting pattern is:
- use
taskto turn a rough request into a task document - use
vetto challenge the task before implementation begins
The visible flow is:
task → vetIn the background, session-distill keeps extracting durable engineering judgment from historical sessions so future task and vet work can benefit from it.
Debugging And Useful Commands
If you want to inspect runtime state or debug the memory system, these lower-level commands are useful:
npm run lx:setup
npm run lx:create-automation
npm run lx:distill-sessionsThere is no longer a supported lx-memory-brief manual command in the current mainline. Generic repository-turn memory consumption now happens automatically through the repo-local Codex hook, while task and vet continue to retrieve memory directly.
Or run:
npm run lx:bootstrap