Lakeside-mem is a local-first memory runtime for software teams. It keeps coding context persistent, retrieves only what matters, and drives stable next actions with evidence.
Quick Start • Most-Used Scenarios • Landing Page • CLI Guide • Architecture • Benchmarks
Legacy compatibility:
Scripts/codex_mem.shstill works.Scripts/dev_mem.shstill works.
- One-click target repository execution (
run-target/run-target-auto) - Persistent project memory across sessions
- Hybrid retrieval: lexical + structure + graph-lite + optional embeddings
- Evidence-grounded output with file/symbol traceability
- Stable output contract with mandatory
forced_next_input
bash Scripts/lakeside_mem.sh init --project demobash /ABS/PATH/TO/lakeside-mem/Scripts/lakeside_mem.sh \
run-target "/ABS/PATH/TO/TARGET_PROJECT" \
--project target \
--question "learn this project: goal, architecture, module map, entrypoint, main flow, persistence, ai generation, tests, risks"bash /ABS/PATH/TO/lakeside-mem/Scripts/lakeside_mem.sh \
run-target-auto "learn this project deeply and return evidence-backed conclusions"These are the most frequent workflows across modern coding-agent usage patterns (onboarding, issue fixing, debug loops, implementation, and repo-scale maintenance).
bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "learn this project: goal, architecture, module map, entrypoint, main flow, persistence, ai generation, tests, risks"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "triage this bug: repro path, root cause chain, minimal-risk fix, validation checklist"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "debug this failure: isolate failing path, show exact evidence, propose smallest fix"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "implement this feature with minimal patch, compatibility boundaries, tests, and rollout notes"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "plan and execute a safe refactor: dependency map, blast radius, incremental steps, regression checks"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "review this change: behavior diffs, hidden risks, missing tests, and release impact"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "reconstruct this incident timeline, identify root cause, and produce a prevention checklist"bash Scripts/lakeside_mem.sh run-target "/ABS/PATH/TO/TARGET_PROJECT" --project target \
--question "generate a handoff: what changed, why, evidence, open risks, and next executable command"ask / run-target output includes:
- completion status (
LEARNING_COMPLETE/PARTIAL/INCOMPLETE) - section coverage report
- evidence stats
- mandatory
forced_next_input - 6-layer runtime metadata (
memory_runtime_layers)
Run MCP server:
python3 Scripts/codex_mem_mcp.py --root . --project-default demoRegister locally:
codex mcp add lakeside-mem -- python3 /ABS/PATH/TO/lakeside-mem/Scripts/codex_mem_mcp.py --root /ABS/PATH/TO/lakeside-mem --project-default demo- prompt compaction saving:
52.86% - scenario max token saving:
99.84% - marketing benchmark saving:
99.84% - runtime pipeline:
4/4stages passed
Run pipeline:
python3 Scripts/benchmark_runtime_pipeline.py \
--root . \
--out Documentation/benchmarks/runtime_pipeline_latest.json \
--checkpoint Documentation/benchmarks/runtime_pipeline_checkpoint.jsonThis is not magic. It is a practical runtime that helps you stop repeating context and start shipping with cleaner evidence.
See repository license file.