Admin access level
Server config contains admin-level keywords
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Persistent semantic memory for Claude Code sessions using LibSQL with vector search.
# Clone the repo
git clone https://github.com/linehaul-ai/libsql-memory.git
cd libsql-memory
# Run Claude Code with the plugin
claude --plugin-dir .
That's it! The plugin will automatically:
/memory-status and /memory-clear commandsNomic embedding server (text-embedding-qwen3-embedding-8b) running at http://192.168.128.10:1234 (default)
Or use local embeddings (no external dependencies):
export LIBSQL_MEMORY_EMBEDDING_PROVIDER=local
claude --plugin-dir /path/to/libsql-memory
Or use OpenAI:
export LIBSQL_MEMORY_EMBEDDING_PROVIDER=openai
export OPENAI_API_KEY=your-key
claude --plugin-dir /path/to/libsql-memory
Copy to your project as a local plugin:
# Copy entire plugin directory
cp -r /path/to/libsql-memory /your/project/libsql-memory
# Then run Claude with the plugin directory
cd /your/project && claude --plugin-dir ./libsql-memory
Or install globally:
claude plugins add https://github.com/linehaul-ai/libsql-memory.git
Provides memory tools:
memory_store - Store a memory with content and namespacememory_retrieve - Get a specific memory by IDmemory_search - Semantic search across memoriesmemory_list - List memories in a namespacememory_delete - Delete a memorymemory_stats - Get storage statistics| Hook | Purpose |
|---|---|
| SessionStart | Loads project context and preferences at session start |
| UserPromptSubmit | Searches memory for context relevant to user queries |
| PreToolUse (Write/Edit) | Retrieves file-specific patterns before code changes |
| PostToolUse (Write/Edit) | Stores architectural decisions and patterns after changes |
| Stop | Saves session summaries and important learnings |
/memory-status - View memory statistics and recent entries/memory-clear [namespace] - Clear memories from a namespace| Variable | Default | Description |
|---|---|---|
LIBSQL_MEMORY_EMBEDDING_PROVIDER | nomic | Embedding provider: nomic, openai, local |
LIBSQL_MEMORY_EMBEDDING_ENDPOINT | http://192.168.128.10:1234/v1/embeddings | Nomic server endpoint |
OPENAI_API_KEY | - | Required if using OpenAI provider |
Stored at .claude/memory.db relative to where Claude Code runs.
Pre-built binaries are included for:
For other platforms, build from source:
cd src/plugin
make build
cd src/plugin
make build # Build for current platform
make test # Run tests
make verify # Run all checks
bin/ directorylocal provider.claude/ directory exists and is writablemake buildMIT
npx claudepluginhub linehaul-ai/libsql-memory --plugin libsql-memoryCreate structured GitHub issues from conversation context with hierarchical sub-tasks and proper formatting.
Project roadmap management with GitHub Projects integration
AI-powered wiki generator for code repositories. Generates comprehensive, Mermaid-rich documentation with dark-mode VitePress sites, onboarding guides, deep research, and source citations. Inspired by OpenDeepWiki and deepwiki-open.
Expert guidance for Golang backend development with Echo Router framework. Provides comprehensive skills for architecture, patterns, and best practices
Comprehensive guidance for building Slack applications with the official Go SDK
Persistent memory for Claude Code. Capture work across sessions and recall relevant context.
Persistent memory system for Claude Code with SQLite, FTS5, and vector search
Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF search with episode batching. Single SQLite DB, no external services. A lighter, lower-cost alternative to claude-mem (episode batching + a smaller model; cost savings are an internal estimate, not a measured benchmark).
memX: local-first semantic memory for coding agents. Native Claude Code lifecycle hooks.
MeMesh — Local memory for Claude Code and MCP coding agents. One SQLite file, zero cloud required.
Persistent local memory for Claude Code. Cross-session recall with vector search, automatic archiving, zero cloud dependencies.