sillogic

Sill Ensoul — AI skill for Claude Code

AI community

Long-term memory for CLI agents — cross-CLI, cross-project, cross-session.

How to install Sill Ensoul

This entry records only its repository, not the path inside it, so there is no exact command to give. Open sillogic/sill-ensoul and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Sill Ensoul does

Long-term memory for CLI agents — cross-CLI, cross-project, cross-session. OKF Wiki + MCP server, model-agnostic.

Alternatives in AI

  • Hindsight — State-of-the-art long-term memory for AI agents by Vectorize 6.7k ★
  • Nocturne Memory — A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents 1.3k ★
  • Metaharness — 🛠️ The meta-harness for AI agents — scaffold your own focused, branded agent harness with its own npx CLI, MC 616 ★

README

Sill-Ensoul

English | [简体中文](README.zh-CN.md)

**Long-term memory that follows your agents across CLIs, projects, and sessions.**

Give your CLI agents experience that doesn't vanish when you switch projects, switch tools, or start a new session — it doesn't touch your workflow, just adds memory to the agents you already use.

*ensoul* /ɪnˈsoʊl/ — verb. To give a CLI agent memory that carries across sessions, so it's more than a blank slate each time. An agent that's been ensouled is called an **ensouler**.


What it does

  • Cross-CLI: one memory, shared across Claude Code / Codex / zcode / Cursor / OpenCode. Use Claude today, switch to Codex tomorrow — your agents' memory follows.
  • Cross-project: memory lives in a global KB, not bound to any project repo. The bug your algo agent hit in project A is recalled in project B.
  • Cross-session: every new conversation, the agent wiki_searches its own past experience first and starts with memory, not from scratch.
  • Agent isolation: spin up multiple ensoulers (algorithm engineer, backend, testing, UI...) — each has its own memory bundle, no cross-contamination. Wake one, work with its experience.
  • Memory is files: plain markdown (following OKF) — git-able, diff-able, editable in Obsidian. Vector stores are just an index; md is always source of truth.
  • Zero external deps: SQLite FTS5 full-text search (CJK char segmentation + BM25) — no OpenAI key, no Docker, no cloud service. Model-vendor-agnostic: inference always stays in your CLI.
  • Proactive distillation: when an agent hits a non-trivial pitfall or makes a reusable decision, it distills and writes it directly, then tells you what it wrote (concept_id + one-line gist). You don't have to remember to write things down, and you keep after-the-fact veto (ask it to delete/edit).

Quick Start

After cloning, do **one** of these in your CLI (