Loom keeps your agents on track.

Loom tutorials

These prompt-first tutorials use the small public Python palmerpenguins repository because it has real package code, tests, and bundled CSV data without requiring a private repository.

You don't need to memorize commands. Practice a repeatable conversation in your coding harness: ask a normal coding question, let the agent check Loom, and confirm that its answer reflects current shared memory. The prompts work in both Claude Code and Codex unless a tutorial calls out a harness-specific step.

Everything you build here runs on the same memory model behind Loom's benchmark scores on STALE, LongMemEval, and AMA-Bench.

How the path works

The order is deliberate. First you establish a safe connection and learn how Loom organizes memory. Then you practice saving and retrieving project knowledge, letting relevant context resurface automatically, and turning repeated work into reusable capabilities. The final tutorials apply those skills to planning, maintenance, and multi-agent coordination.

Store names vary by account. Tutorial 02 shows how to list, load, describe, and unload your stores without replacing the default store for the session.

Tutorial format

Every walkthrough uses the same three-part format:

YouThe prompt you type into your coding harness.
AgentWhat the agent does with Loom or the opened repository.
ResultThe answer you should expect to review.

End every session with a capture pass

Memory compounds when you close the loop. At the end of a working session, use this prompt:

YouReflect on this session and capture any important Decisions, Findings, or Directives in Loom if they are not already there.
AgentThe agent checks current memory on the topics covered, then saves only durable information that is not already captured: a decision made, a rejected option worth remembering, a root cause found, a non-obvious gotcha, or a directive given. It skips status chatter and facts already evident from code or git history.
ResultI checked current Loom memory first and captured only the durable information that was not already present. If the session added no durable decision or verified finding, nothing needed saving.

Run this as a habit, not as a demand to create a fact every time.

Follow the tutorial path

Back to Loom Cloud