llm-kosh
Allows publishing and verifying artifacts through GitHub Actions workflows.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@llm-kosh search for notes about the API design"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Why this exists
AI agents can reason across increasingly long workflows, but their memory is often either ephemeral or delegated to opaque hosted services.
LLM-Kosh treats memory as local infrastructure: inspectable, portable, auditable, permissioned, and usable across MCP-compatible clients.
It gives agents a durable memory layer built from ordinary local files plus structured indexes and governance controls:
Local-first — your cartridge stays on your machine by default.
Inspectable — memory remains readable, backupable, diffable, and reviewable.
Auditable — mutations are recorded in a tamper-evident ledger.
Permissioned — MCP starts read-only; write, mutation, and private export require explicit opt-in.
Portable — one cartridge can support multiple compatible AI clients and workflows.
Evidence-aware — Kosh Verify can distinguish support, contradiction, inference, evidence gaps, and absence.
Install it:
python -m pip install --upgrade llm-kosh
Related MCP server: mnemo
Kosh Verify: memory that can show its work
Long-lived memory creates a different failure mode from a one-off bad answer: a weak or misunderstood memory can be recalled again in later sessions.
Kosh Verify is LLM-Kosh's evidence-aware verification surface. Given the evidence already present in a cartridge, it can produce a structured report containing temporal context, supporting facts, causal paths, contradictions, inferred-but-not-discovered relationships, missing evidence, stability information, and an explicit abstention state when there is not enough evidence.
It is not a universal truth oracle and it does not make an imported source trustworthy simply because it was stored. The aim is to preserve the difference between what the cartridge observed, what it inferred, what conflicts, and what it cannot support.
Try the deterministic synthetic incident demo:
llm-kosh --root ./kosh-demo kosh-verify \
"Why did checkout fail and what evidence contradicts the explanation?" \
--when "2026-05-01T13:30:00+00:00" \
--depth 5 \
--demo-seed \
--json--demo-seed writes synthetic incident evidence into the selected root, so use a disposable directory. The same behavior is covered by automated tests and a network-free acceptance harness:
python scripts/kosh_verify_acceptance.pySee Kosh Verify for the contract, boundaries, API example, MCP surface, and reproducible checks.
What makes LLM-Kosh different
Capability | LLM-Kosh |
Local-first persistent memory | ✅ |
MCP-native access | ✅ |
Human-inspectable storage | ✅ |
Tamper-evident mutation ledger | ✅ |
Read-only-by-default agent access | ✅ |
Evidence-backed context packs | ✅ |
Temporal/causal verification | ✅ |
Contradiction and evidence-gap reporting | ✅ |
Explicit no-evidence abstention | ✅ |
Hosted memory service required | ❌ |
Automatic cloud sync required | ❌ |
Architecture
flowchart TB
A[AI client / agent] -->|MCP| R[Access layer]
M[CLI] --> R
N[Background service] --> R
O[Local HTTP MCP - optional] --> R
subgraph KOSH[LLM-Kosh]
R
C[Memory]
D[Evidence]
E[Search]
F[Policy]
G[Ledger]
H[Context packs]
V[Kosh Verify]
R --> C
R --> D
R --> F
C --> E
C --> G
C --> H
C --> V
D --> V
end
C --> I[(Local cartridge)]
D --> I
E --> I
G --> I
I --> J[Plain files]
I --> K[SQLite / FTS]
I --> L[Audit ledger]The repository root contains the code. The cartridge root contains the live memory store. Watched intake folders can feed new material into the cartridge without mixing runtime data into the source checkout.
60-second quickstart
Python 3.10 or newer is required.
python -m pip install --upgrade llm-kosh
llm-kosh install --yes
llm-kosh statusThat installs the package, creates the default cartridge at ~/.llmkosh/cartridge, configures local defaults, and registers supported desktop integration where possible.
Create and query a custom cartridge:
llm-kosh --root ./my-cartridge init --owner "Local User"
llm-kosh --root ./my-cartridge add --kind note --title "First memory" --body "Hello"
llm-kosh --root ./my-cartridge query "Hello"Manage the background service:
llm-kosh service start
llm-kosh service status
llm-kosh service stopWhat works today
The core project is usable now:
Python package published as
llm-koshlocal CLI for creating, searching, importing, packing, and verifying cartridges
governed
llm-kosh-memoryCLI for proposing, recalling, inspecting, conflicting, and explicitly reviewing Trusted MemoryKosh Verify CLI and Python API for evidence-aware temporal/causal verification
deterministic Kosh Verify incident demo and acceptance tests
local MCP server with explicit write, mutation, and private-export capability gates
source-level MCP composition that adds read-only
kosh_verifyplus governed Trusted Memory tools without changing those gatesbackground service for intake and maintenance jobs
plain-file, inspectable storage with local indexes
tamper-evident mutation ledger
GitHub Actions test, quality, security-scanning, and publishing workflows
experimental company-brain foundation for evidence-backed memory and cited context
The remaining release work is primarily desktop packaging polish and signing across Windows, macOS, and Linux. The llm-kosh-mcp and llm-kosh-memory entry points described here are present on current master source and are intended for the next package release; the currently published PyPI 2.1.3 package predates those entry points.
Use with MCP clients
The currently published package exposes the standard MCP server through the existing CLI:
llm-kosh --root ./my-cartridge mcp-serverOn current source, the composed MCP entry point exposes the standard server, read-only kosh_verify, and governed Trusted Memory tools:
python -m pip install -e .
llm-kosh-mcp --root ./my-cartridgeEquivalent module invocation:
python -m llm_kosh.mcp_trusted_memory_server --root ./my-cartridgeThe Trusted Memory MCP surface is deliberately permissioned:
trusted_memory_recall,trusted_memory_inbox,trusted_memory_conflicts, andtrusted_memory_explainare read-only.trusted_memory_proposerequires--allow-write.trusted_memory_reviewrequires--allow-mutate.agent-created proposal evidence is recorded as
agent_observation, never self-elevated touser_direct.explicit review can change lifecycle without rewriting the original source authority; strict recall still requires authoritative/trusted evidence.
Kosh Verify does not require additional privileges. Write, mutation, and private-export capabilities remain opt-in and continue to use the standard server flags:
llm-kosh-mcp --root ./my-cartridge --allow-write
llm-kosh-mcp --root ./my-cartridge --allow-write --allow-mutate
llm-kosh-mcp --root ./my-cartridge --allow-privateThe composed server also supports local streamable HTTP:
llm-kosh-mcp --root ./my-cartridge --http --port 8000
# endpoint: http://127.0.0.1:8000/mcpTreat HTTP transport as a real network boundary if you expose it beyond loopback. See Trusted Memory over MCP for the governed memory contract, Kosh Verify for the kosh_verify contract, and MCP guide for general MCP setup.
Company-brain foundation
The experimental company-brain layer extends the cartridge beyond simple note recall. It introduces reference-first evidence, session and episode understanding, evidence-backed memories, review lifecycles, permission-first retrieval, and structured cited context packs.
Migrate an existing cartridge:
llm-kosh --root ./my-cartridge brain migrate --dry-run
llm-kosh --root ./my-cartridge brain migrate
llm-kosh --root ./my-cartridge brain health
llm-kosh --root ./my-cartridge brain context "Prepare the next project decision"Register existing files without copying their source bytes:
llm-kosh --root ./my-cartridge brain register ./report.xlsx --artifact-type worksheet
llm-kosh --root ./my-cartridge brain inspect <evidence-id> \
--locator '{"sheet":"Summary","range":"A1:F25"}'
llm-kosh --root ./my-cartridge brain evaluateBuild a replayable session or episode graph from a registered JSONL export:
llm-kosh --root ./my-cartridge brain register ./session.jsonl --artifact-type structured_data
llm-kosh --root ./my-cartridge brain understand <evidence-id> --dry-run
llm-kosh --root ./my-cartridge brain understand <evidence-id>
llm-kosh --root ./my-cartridge brain episodes --query "what was implemented"Core concepts
Three locations matter:
Repository root — the source checkout.
Cartridge root — the live memory store selected by
--rootorLLMKOSH_ROOT.Watched intake folders —
receipts/,intake/, and configured external drop folders.
If files are dropped into cartridge intake areas, the service can process them asynchronously. External folders can also be watched through [daemon].watched_directories.
Optional features
python -m pip install "llm-kosh[watch]" # filesystem events
python -m pip install "llm-kosh[server]" # FastAPI service
python -m pip install "llm-kosh[semantic]" # local semantic search
python -m pip install "llm-kosh[ingest]" # document conversion helpers
python -m pip install "llm-kosh[all]" # all optional featuresMCP support is included in the base installation.
Security model
LLM-Kosh is intentionally conservative around agent privilege and export boundaries:
storage and search are local by default
there is no automatic cloud sync or package telemetry
MCP starts read-only
write, mutation, and private-export capabilities require explicit opt-in
optional HTTP transport is a real network boundary and should be configured accordingly
exported context is checked for common secret patterns before sharing
cartridge files are plaintext by design, so use operating-system disk encryption when local data at rest requires encryption
See SECURITY.md for the canonical threat model, reporting guidance, and current security boundaries.
Project status
LLM-Kosh is actively maintained open-source infrastructure for durable agent memory.
The Python package, CLI, MCP server, local service, Kosh Verify surface, test workflow, and publishing path are operational. Current work focuses on interoperability, packaging, governed memory, evidence-aware verification, and making the project easier for external contributors to extend safely.
The Electron desktop app is packaged separately from the Python package. Local developer builds and Windows installer smoke tests are supported; public GA desktop distribution still requires verified Windows code signing and macOS Developer ID signing/notarization.
See GA_READINESS.md for the detailed release posture.
Developer workflow
python -m pip install -e ".[server,watch,ingest]"
python -m pytest -qRun the small public verification acceptance contract separately:
python scripts/kosh_verify_acceptance.pyFor packaging or release changes:
python -m build
python -m twine check dist/*Native C++ math acceleration is optional. Set LLM_KOSH_BUILD_NATIVE=1 and install pybind11 before building to test it. Release wheels use the portable pure-Python fallback.
Contributing
Contributions are welcome, especially around:
MCP interoperability
tests and regression coverage
packaging and cross-platform reliability
documentation
local-first memory workflows
security hardening
evidence and retrieval quality
reproducible verification and benchmark methodology
Please read CONTRIBUTING.md before proposing substantial changes. Use GitHub Issues for reproducible, non-sensitive bugs and feature proposals, and follow SECURITY.md for security-sensitive reports.
Documentation
Guide | Purpose |
First installation and local use | |
Evidence-aware verification contract and reproducible demo | |
Governed cross-agent recall, proposal, conflict, and review over MCP | |
System structure and design | |
Command reference | |
MCP setup and usage | |
Development workflow | |
MCP internals | |
Background service internals | |
Desktop packaging | |
Build and release process | |
Threat model and reporting | |
Current release posture | |
Historical material |
Open source
LLM-Kosh is maintained in the open under the MIT License.
Bug reports, focused pull requests, interoperability improvements, tests, and documentation contributions are welcome.
Available Tools
36 toolsapply_intake_proposalC
Directly applies an intake proposal batch to the live memory.
Inputs: batch_id (required).
company_artifact_inspectC
Verify and inspect a bounded region of an authorized registered artifact.
Inputs: evidence_id (required), max_text, clearance, tenant_id, +5 more.
company_artifact_registerB
Register an existing local artifact by fingerprint without copying its bytes.
Inputs: file_path (required), tenant_id, artifact_type, classification, +1 more.
company_artifact_segmentC
Inspect an artifact and persist bounded derived segments with native citations.
Inputs: evidence_id (required), max_text, clearance, tenant_id, +4 more.
company_artifact_snapshotC
Explicitly materialize an authorized artifact into immutable snapshot storage.
Inputs: evidence_id (required), clearance, tenant_id, groups_json, +2 more.
company_brain_evaluateB
Run reference storage, citation, and projection acceptance checks.
Inputs: no named parameters.
company_brain_healthB
Validate canonical company-brain storage and projection consistency.
Inputs: no named parameters.
company_context_compileD
Compile structured, cited, token-budgeted context for an agent task.
Inputs: task (required), as_of, clearance, tenant_id, +7 more.
company_episode_getB
Get one authorized episode with ordered event and candidate provenance.
Inputs: episode_id (required), clearance, tenant_id, groups_json, +2 more.
company_episodes_searchC
Search authorized goal-oriented work episodes and observed outcomes.
Inputs: limit, query, clearance, tenant_id, +4 more.
company_memory_getB
Get one authorized memory with its evidence references and lifecycle.
Inputs: memory_id (required), clearance, tenant_id, groups_json, +2 more.
company_memory_proposeC
Create immutable evidence and a non-authoritative candidate memory.
Inputs: title (required), statement (required), memory_type (required), evidence_content (required), +6 more.
company_memory_propose_from_evidenceC
Create a candidate semantic memory citing an existing registered artifact.
Inputs: title (required), statement (required), evidence_id (required), memory_type (required), +10 more.
company_memory_reviewC
Apply a governed lifecycle transition to an authorized memory.
Inputs: reason (required), memory_id (required), to_lifecycle (required), clearance, +4 more.
company_memory_searchC
Permission-first hybrid search over atomic, evidence-backed company memory.
Inputs: query (required), as_of, limit, clearance, +7 more.
company_sessions_listC
List authorized normalized source sessions.
Inputs: limit, clearance, tenant_id, project_id, +3 more.
company_session_understandC
Build normalized sessions, episodes, and cited candidates from JSONL evidence.
Inputs: evidence_id (required), dry_run, clearance, tenant_id, +7 more.
create_private_context_packC
Creates a highly focused context pack for a specific task. Includes private and sensitive information.
Inputs: query (required), target.
get_cartridge_memory_mapB
Returns a structural map of the knowledge base projects and active concepts.
Inputs: no named parameters.
get_daemon_statusC
Verifies the cryptographic ledger of the Cartridge.
Inputs: no named parameters.
get_project_contextC
Fetches all context and active decisions for a specific project.
Inputs: project_name (required).
intake_convert_fileC
Converts a local file (e.g. PDF, DOCX, XLSX, PPTX, PNG, WAV) to structured markdown using the MarkItDown converter and ingests it into the cartridge.
Inputs: file_path (required), project.
kosh_verifyC
Verify a question against local temporal/causal evidence.
This is read-only. The returned JSON report can include supporting facts, causal paths, contradictions, inferred-but-not-discovered relationships, missing evidence, stability information, and an explicit abstention state.
It does not consult the internet, seed demo data, write or mutate memory, export private context, or make an imported source trustworthy.
Inputs: query (required), depth, dialectic, temporal_context.
list_intakeB
Lists the current items pending in the intake queue.
Inputs: status.
reasoning_critiqueA
Run the Lyapunov critic on a specific list of fact IDs. Returns stability score, status, and per-dimension breakdown.
Inputs: fact_ids (required).
reasoning_exploreB
Enumerate all causal paths between two known facts. Returns the fiber bundle for that specific pair.
Inputs: to_fact_id (required), from_fact_id (required), max_hops.
reasoning_ingestA
Add a bounded atomic fact to the Temporal Causal Reasoning Graph. This is a write operation and requires --allow-write. documented_at and valid_from are ISO 8601 datetime strings. causal_edges: JSON array of {"target_id": str, "edge_type": str, "confidence": float}. Returns the new fact_id.
Inputs: content (required), valid_from (required), documented_at (required), confidence, +2 more.
reasoning_queryB
Query the Temporal Causal Reasoning Graph. By default returns a human-readable causal narrative (narrative=True). Set narrative=False to get raw JSON with full fiber bundle details. temporal_context: ISO 8601 datetime or Unix timestamp string (omit for now).
Inputs: query (required), depth, narrative, temporal_context.
search_memoryC
Search the Cartridge Knowledge Base for memories, decisions, and files.
Inputs: query (required), limit, use_semantic.
submit_memory_receiptA
Submits a MEMORY_RECEIPT.md formatted string to the intake queue. Does not apply it directly; it must be reviewed and applied.
Inputs: receipt_content (required).
trusted_memory_conflictsC
List unresolved authorized Trusted Memory conflicts.
Inputs: limit, query, clearance, tenant_id, +4 more.
trusted_memory_explainB
Explain one authorized memory with evidence and admission history.
Inputs: memory_id (required), clearance, tenant_id, groups_json, +2 more.
trusted_memory_inboxB
List authorized candidate and quarantined Trusted Memory items.
Inputs: limit, query, clearance, tenant_id, +4 more.
trusted_memory_proposeA
Propose governed memory. Requires MCP write capability.
If evidence_id is omitted, the proposal is persisted as an
agent_observation. Agents cannot self-label new MCP evidence as
user_direct. To preserve a stronger or different source type, register
evidence first and pass its existing id.
Inputs: title (required), statement (required), memory_type (required), subject, +14 more.
trusted_memory_recallC
Recall governed memory with admission and lifecycle policy enforced.
Inputs: mode, as_of, limit, query, +7 more.
trusted_memory_reviewC
Explicitly approve, quarantine, reject, or supersede governed memory.
Requires the existing MCP mutate capability. Conflict resolution is never inferred from a generic approval.
Inputs: action (required), reason (required), memory_id (required), clearance, +5 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 36 tools
There are multiple overlapping retrieval and governance clusters: search_memory, company_memory_search, trusted_memory_recall, and kosh_verify all serve different-but-similar memory/questioning purposes, while company_brain_health and company_brain_evaluate appear nearly interchangeable. The trusted_memory_* and company_memory_* families further blur boundaries around 'governed memory' vs 'company memory'.
Naming mixes several patterns: verb-first (search_memory, list_intake), noun-first domain actions (trusted_memory_propose, company_memory_search), and prefix-plus-verb (reasoning_query, intake_convert_file). Although all names are snake_case, the inconsistent ordering and domain-prefix placement make the surface harder to predict.
36 tools is heavy for a single MCP server, spanning at least four major subsystems: cartridge/intake, trusted memory, company memory/artifacts, and causal reasoning. Many tools could reasonably be split into separate servers, and the count creates cognitive load and selection risk.
The server covers many lifecycle stages across memory, evidence, artifacts, intake, and reasoning, including propose/review/recall/search and artifact registration/inspection/snapshot. However, there are notable gaps such as no direct memory deletion/update, no artifact listing, and no project listing beyond a structural map.
Maintenance
Related MCP Connectors
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
Persistent, verbatim, searchable memory for AI assistants — one memory across every MCP client.
Persistent, portable memory for AI assistants — your private memory graph, from any MCP client.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.3MIT
- AlicenseNot gradedqualityDmaintenanceA local-first memory server for AI tools that provides cross-tool, consent-gated, and auditable memory management via MCP.AGPL 3.0
- AlicenseAqualityBmaintenanceMCP server for persistent, cross-session, local-first memory for AI agents, storing memories as Markdown files with SQLite indexing for hybrid search.24Apache 2.0
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0