changelog · new threads

What shipped, and what is still on the loom.

This page tracks the repository, honestly. What is built is listed as shipped; what is not appears under next.

v1.3.3 current apache-2.0

the context engine

Recall · deterministic retrieval over your session history: full-text search across messages, one hop through the session graph, distilled notes and human pins, packed to a token budget with a reason given for every item. No embeddings, no vector store, no API key
MCP server · five tools your agents call themselves, installed into Claude Code, Codex and Cursor by one command, with every edited config backed up first. Hand-rolled JSON-RPC, zero new dependencies
Ask a session · resume any past session read-only on the machine that owns it, and get an answer from the agent that lived it rather than a summary of it
Benchmark harness · a measured corpus of real session history, so retrieval quality is a number rather than a feeling

hand off

Both directions · native writers for Claude Code and Codex, so a session crosses either way and the target tool treats it as its own history
To a teammate · hand a session to a person, not just a tool. It lands in their editor through their own daemon, and the command waits for the outcome instead of assuming it
Digest mode · long sessions travel as a condensed history with a verbatim tail

collect, on your terms

Readers for Claude Code, Codex and Cursor · every session indexed as it lands
Personal by default · joining a team shares nothing until you promote a project to it. Visibility is enforced on every read path, and marking a project team-visible now reaches the sessions that were already synced
Secret redaction on by default · ten high-precision patterns, applied on the source machine before upload
Retention · prune by age, exclude a path, and purge what was already synced

the team surface

Self-hosted server · one process and one SQLite file on port 4680, live over SSE
Pinned notes · comment on a session or a single message, mention a teammate, and never touch the transcript
Session memory · entity notes for files, decisions and topics, with supersession and conflict flags. Pluggable provider, off by default
Dashboard · sessions, people, memory, search and setup, in light and dark

the workshop

motif doctor · eight checks, each with the command that fixes it
Ops · docker compose, daemon install for macOS and Linux, status, pause and resume
103 tests across fifteen files, CI on Node 22 and 24 across Linux, macOS and Windows · four runtime dependencies · no telemetry
Published to npm as getmotif, from CI, with a provenance attestation tying the tarball to the commit it was built from

releases

1.3.3 · drag a node in the Weave: grab a knot and its ties stretch with it, the rest resettling when you let go
1.3.2 · the Weave reads more clearly. The same concept seen in two projects is one knot rather than two, so cross-project ties pull together, and a hover card gives any node its kind, confidence and tie count
1.3.1 · an Overview home page, so the first screen says what happened and what needs a human. The Weave stopped burning frames at rest
1.3.0 · memory gained a confidence number and the graph gained causal edges, and the loop closed: a Weaver pull request's fate feeds back into the memory it came from
1.2.0 · the feature release. The Weave, the record drawn as a graph. The Weaver scanning for changes the repo never tested and queueing them as draft PRs. The review loop: confirm, prefer, retire and dispute, from the CLI or a new Review inbox. Staleness, computed without a model call. Plus motif demo and motif blame. Also fixed: entity names distilled from personal sessions were listed for every token holder, so notes now inherit the visibility of their evidence
1.1.3 · engines still said Node 20 while the SQLite prebuilds started at 22, so a Node 20 install compiled from source without saying so
1.1.2 · installing on Node 24 compiled SQLite from source. Moved to the release line that covers Node 22 through 26, and CI now tests both
1.1.1 · doctor called a working local token missing when the server was unreachable; the daemon dropped --claude-dir
1.1.0 · security release. Re-enrolment could exchange the read-only team token for the owner's credential; personal session titles and paths reached every event subscriber; the ask path trusted its input. All fixed, and SECURITY.md now states plainly that this is a trust model rather than a sandbox. Anyone running a shared server should be on this or later
1.0.6 · marking a project team-visible did nothing to sessions already synced, which on a fresh machine is all of them

fig. i · what the loom has finished

Versions follow the repository, not marketing. When something is not built yet, it appears under next, never above it.

← back to the pattern