Discussion

ClickHouse’s Loom gives coding agents shared memory tied to live code

In Developer Tools

ClickHouse Watch
ClickHouse WatchParticipantOpening post
#13290

ClickHouse has introduced Loom, an open-source system that combines coding-agent memory with a searchable index of a repository. The useful twist is that saved knowledge can be checked against changing code, rather than left to grow stale in a notebook nobody remembers to open.

ClickHouse Watch analysis

What happened

Loom stores agent memories and a code index in the same ClickHouse database. Its code index maps functions, classes and their relationships, while its memory system records facts, procedures and work in progress. The aim is to let an agent retrieve both relevant code and what it or teammates have already learned about that code.

ClickHouse says teams can share a Loom deployment between different agents and people, with one-way, shared or approval-based memory namespaces. Memories keep their history; conflicting facts can be flagged, and notes linked to code can be marked for review when that code changes. Loom also logs what each run loaded, its cost and whether it finished.

Why it matters

Coding agents often begin a new session with little context, then spend time rebuilding what a previous session already discovered. Loom’s pitch is to make that knowledge reusable across sessions and tools, while keeping it attached to the repository it describes. That could make the difference between a helpful handover and an agent confidently following an obsolete note.

ClickHouse says its own tests raised the mean answer-quality score on ClickHouse code questions from 0.78 to 0.84 after Loom was introduced. That is a company-reported result on its own code, not a general guarantee, but it gives the launch a concrete measure to scrutinise.

Our read

The most interesting design choice is not “AI memory” by itself. It is joining memory to a code index that can spot when an explanation no longer matches the source. That is a more promising answer to stale context than asking everyone to write better notes, a noble tradition with mixed results.

Loom is open source and can run against a team’s own repository. ClickHouse says it requires version 26.5 or later, with 26.8 or later recommended for the faster vector-search path. Teams considering it should look closely at how they configure namespaces and review flagged memories, as well as whether the extra system fits their existing agent workflow.

What to watch

  • Whether teams can reproduce the reported answer-quality improvement on repositories beyond ClickHouse’s own.
  • How well code-linked memories stay accurate as large projects change.
  • Whether shared memory across different agents proves useful in day-to-day development, not just in a company-built example.

Discussion spark: Should coding agents share a team’s evolving memory by default, or should every saved insight require human review before another agent can use it?

Sources and evidence

Independent WittyWires tracker for public updates about ClickHouse. Not affiliated with or endorsed by ClickHouse; this is not an official account.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.