What's included
This page lists Loom’s main capabilities, self-hosted from the Apache-2.0 repository: one section per area, each row linked to the page that covers it. The docs index maps the rest of the docs. Several capabilities must be turned on; the linked page says how, and the boolean switches that load false are listed in status. The embedder is your choice: the bundled local model, a hosted provider or an OpenAI-compatible endpoint you run. Extraction, summaries and cited answers need a real LLM (models and API keys).
Memory
| Capability | What it does | Page |
|---|---|---|
| Shared long-term memory | One claim per key in a namespace, judged against the facts already there before it lands | Writing memory |
| Typed records | Rows with exact fields for data that has identity, answering predicate questions without parsing text | Typed records |
| Search and ask | Ranked hits, or an answer that cites memory keys; both abstain when memory does not support one | Search and ask |
| Conflicts and refusal | A close but different value is flagged and the namespace owner decides which fact stands; a registered pattern refuses matching writes | Conflicts and refusal |
| History and provenance | Every write is a new version, with who wrote it and how it entered memory | History and provenance |
| Extraction from transcripts | The server decides what in a transcript is durable | Extraction |
| Import | Facts another memory system already distilled, written with the same checks as any write | Importing |
| Change webhooks | A signed event when a memory is written, revised, deleted, restored, redacted or erased, posted to a URL a namespace admin registers | Change webhooks |
| Working memory and profiles | Small named blocks and profile text an agent is given every time | Working memory and profiles |
| Procedures and learnings | Steps learned from reported runs, reflections and a review queue of candidate facts | Procedures and learnings |
| Memories linked to code | A memory about code follows the definitions it names as they move or change | Memories linked to code |
| Entity graph | Entities and their relations beside the memory rows | Entity graph |
Documents, code and work records
| Capability | What it does | Page |
|---|---|---|
| Document search | Documents split into sections, embedded, searched and cited by passage; searches that found nothing are grouped into knowledge gaps | Knowledge documents · Knowledge gaps |
| Files and document sources | PDF, DOCX, PPTX, XLSX, CSV and more parsed by an extractor service; registered sources synced into a namespace | Ingesting files · Document sources |
| Unified search | Memory, profile, documents and past conversations in one call, and a context pack for a task | Unified search |
| Ask AI | An assistant in the dashboard that answers about what a namespace holds, with a citation for every claim; its model and tool loop run in Loom | Dashboard · Assistant setup |
| Code index | Definitions, callers, impact and search by meaning over your git repositories | Code index |
| PR and release history | Merged pull requests joined against today’s symbols, callers and tests | History, PRs and releases |
| Tracker | Issues, pull requests, incidents and CI runs read live from your own ClickHouse | Tracker plane |
| Conversations and sessions | Searchable verbatim transcripts, recorded once an admin turns logging on for the namespace, and session briefs an agent resumes from | Conversations and sessions · Recording |
| Runs | One record per task execution, with the memories it relied on | Runs |
| Tasks, decisions and policies | Task inboxes, a decision record and policies for coordination between agents | Tasks, decisions and policies |
Access, governance and operations
| Capability | What it does | Page |
|---|---|---|
| Namespaces and sharing | The unit of isolation and sharing inside an org; every read is scoped to one | Namespaces and sharing |
| Tokens and roles | Tokens, grants and roles per namespace | Tokens and grants |
| Single sign-on and SCIM | OIDC sign-in for the dashboard, CLI and MCP clients, and deprovisioning through SCIM | Single sign-on |
| Audit log | One row per audited operation or server event, its free-text values stored as hashes, sealed into a verified checkpoint chain | Audit log |
| Retention and erasure | Expiry, configured retention, and erasure of a scope everywhere Loom keeps it | Retention and erasure |
| Sensitive values | A high-sensitivity memory is never embedded and is readable by key only, with an audited read; detection is configurable |
Memory types |
| Model-call controls | An org admin can switch off every model call for the org’s data, and a deployment can route them through an inference gateway | Switching model calls off · Inference gateway |
| Cost and usage | Every embedding and LLM dollar recorded against the operation that spent it | Cost and usage |
| Telemetry | A per-operation ledger, OpenTelemetry traces, logs and metrics, and query attribution | Telemetry |
| Dashboard | The web app where people decide conflicts, proposals, tasks, grant requests and policies | Dashboard |
| SQL access | Read-only ClickHouse views over a tenant’s memories, history, conversations and request ledger, also readable from Postgres | SQL surface · Query from Postgres |
| Replicas and Kubernetes | Identical replicas behind one URL, and a Helm chart | Running N replicas · Kubernetes |
| Postgres memory authority | Optional: live memory and document heads in Postgres, chosen at first boot | Postgres |
| Backup and recovery | ClickHouse backups, plus the document bucket and Postgres where used | Backup and recovery |
| Upgrades | The image is replaced and its migrations apply at boot; a fresh install takes the same path | Upgrades |
| Namespace copy and OKF bundles | A namespace copied to another Loom on a schedule, or exported and imported as an OKF bundle | Copying a namespace · OKF bundles |
| Usage export | One UTC day of usage and a snapshot of the namespaces, written to S3 as Parquet for a data warehouse | Analytics export |
Ways to connect
MCP for any MCP client, plugins for Claude Code and Codex, framework adapters, an HTTP API,
Python and TypeScript SDKs, and the loom CLI:
Integrations ·
MCP clients ·
Frameworks ·
HTTP API · Python SDK ·
TypeScript SDK · CLI.