Use cases and roadmap

Point your coding agent at Loomtracer, and it records the why as it works.

Concrete ways one person and their agents put Loomtracer to work: what works today, what is coming next, and what is planned. Every card for today shows the actual command of Loomtracer’s command-line tool, loomtracer, or the tool call; the drawings are made-up examples.

Works today in v0.8.0 (23 Oct 2026) Coming next merged or under way, not yet released Planned decided, not built

In the drawings: works today PLANNED not built

What works today

v0.8.0

Every write says who made it and is never edited or deleted. Status (proposed, accepted, contested, superseded) follows from the record, never from a label somebody sets by hand.

Works today

Record the decision as you work

Agent

Mid-task, your agent records the choice, the options it weighed and why, and what the decision rests on, without leaving the session. It records who decided: you, or the agent.

capture_decision(title, rationale, options, chosen_option_label, grounding, decided_by)
Works today

Ask "why did we choose this?"

Human · Agent

In a fresh session, with no chat history: the rationale, the options chosen and rejected, who decided, and whether it still holds. Describe the decision; no id needed.

loomtracer query why "sqlite for local storage"
Works today

Ask "did it hold up?"

Human · Agent

Whether the decision still stands, or was replaced, disputed, or rests on a premise that no longer holds. With the reasons, from the record.

loomtracer query verify "sqlite for local storage"
Works today

Disagreement stays on the record

Human · Agent

Push back on a decision and both sides are kept. It reads contested, a state you can ask about, not a lost thread.

loomtracer disagree "sqlite for local storage" --reason …
Works today

Replace without erasing

Human · Agent

Record the new decision as replacing the old one. The old one reads superseded and says what replaced it; the whole chain stays, and you can follow it back to the first proposal.

loomtracer supersede "sqlite for local storage" --title … --rationale …
Works today

Every decision says what it rests on

Human · Agent

An earlier decision, something observed, an assumption, or a bet with a date to check. When that premise is later replaced or refuted, the decisions built on it read stale. The capture plugin makes your agent answer this before it records: with nothing to go on, it records a bet, not made-up evidence, and asks you for the reason. A capture that names nothing is refused.

loomtracer emit decision.capture … --rests-on-decision "ids never change"
Works today

"What should I know before I touch this?"

Agent

The decisions about the files your agent is changing, read from the current diff. No question to type, and each one says whether it still holds.

loomtracer query situational
Works today

Several projects, one record

Human · Agent

Every decision carries its project. A question asked from one project also looks in the project it is part of and the ones it depends on, one hop, and says where it stopped looking.

loomtracer query situational --project mobile-client
Works today

Look over a week of agent decisions

Human

What your agents decided this week, one by one: accept, dispute or replace each, in the terminal, without watching them live.

loomtracer review --actor 'agent:*' --since 7d
Works today

The decision log as Markdown

Human

Export every decision as a tree of Markdown files grouped by project, an index first. Readable without Loomtracer, and it can live in your repo.

loomtracer export --format markdown --out ./decisions/
Works today

Turn existing notes into decisions

Human

Import the Decision: blocks from your docs. Each becomes a decision carrying its source, and lands as unreviewed until you look at it.

loomtracer import documents ./notes/
Works today · experimental

Import decisions from living documents

Human

Pull decision candidates from a Google Doc or a file in git history. Each import records the source at the revision it read, so the citation stays honest as the document moves. Google Docs only; Confluence is not supported yet.

loomtracer import connector run --url <gdocs-url>
Works today

A disagreement travels

Human · Agent

When a decision is replaced or disputed, every decision resting on it gets an open re-examine item, closed only by an explicit "still holds" or by its own replacement. The replaced decision shows how many of them are done, so a half-finished reversal is visible instead of quietly forgotten.

loomtracer reexamine
loomtracer reaffirm "cache records by id" --because …
Works today

How well made was this decision?

Human · Agent

A profile on seven dimensions: framing, alternatives, information, reasoning, values and trade-offs, bias exposure, calibration. Each line names the recorded facts it was read from, and says "not assessed" where there is nothing to read. Not a grade, and never a mark against changing your mind.

loomtracer query score_decision --id …
Works today

An honest bet, called out

Human · Agent

With nothing yet to rest a decision on, name a bet and a date to check it. Calling it out is expected, not blame. Once the date passes, it is listed among what needs a look.

loomtracer query get_suggestions
Drawn: a bet with a date
  1. 1 · Before

    Readers will pay5 € a month a bet · check by 1 Novwrong if under 100 pay 5 € a month forthe newsletter rests on

    You start charging 5 € a month for your newsletter. Nothing shows yet that readers will pay, so the decision rests on a bet, with a date to check it and what would prove it wrong.

  2. 2 · 1 November passes

    Readers will pay5 € a month a bet · check by 1 Novwrong if under 100 pay past its check date 5 € a month forthe newsletter needs a look rests on

    Nothing was recorded either way. Ask about the decision and the bet reads past its check date, and Loomtracer lists it among what needs a look, without being asked.

  3. 3 · Evidence arrives

    Readers will pay5 € a month a bet · check by 1 Novwrong if under 100 pay held 5 € a month forthe newsletter still holds 212 readers payafter a month seen in: payments, 3 Nov rests on supports

    212 readers pay after a month. The evidence supports the bet, which reads held. Had it gone the other way, it would read failed.

Works today

Questions nobody has decided yet

Human · Agent

Ask a question before anything answers it, and it waits, with its age, until a decision answers it. What is contested and what changed are lists of their own.

loomtracer ask "Open on Sundays?"
loomtracer query get_waiting_requests
Drawn: questions still waiting
  1. 1 · You ask

    Which flour supplier? asked 23 Sep Raise the priceof a loaf? asked 25 Sep Open on Sundays? asked 27 Sep

    Over a week you ask three questions about your café. Each is recorded when you ask it, before anything answers it.

  2. 2 · One is answered

    Which flour supplier? asked 23 Sep Raise the priceof a loaf? asked 25 Sep answered Open on Sundays? asked 27 Sep A loaf costs20 cents more answers

    You decide a loaf costs 20 cents more. The decision answers that question, and the question reads answered.

  3. 3 · What is still waiting

    Which flour supplier? asked 23 Sep asked 6 days ago · waiting Raise the priceof a loaf? asked 25 Sep Open on Sundays? asked 27 Sep asked 2 days ago · waiting A loaf costs20 cents more answers WAITING, OLDEST FIRST

    On 29 September the waiting list shows the two open questions, oldest first, each with its age. A list, not a grade: no averages, and nobody is ranked.

Coming next

Built, not yet released, or under way

Merged and waiting for the next release, or being built now. Shown as intent until it is in a release you can install.

Coming next

A much simpler, decision-first UI

A list of decisions, newest first, as the start page, scoped by project. One decision's neighbourhood as the graph, with every arrow running from newer to older. Less clutter.

Coming next

Capture that runs all day

Your sessions with your agents are read as they happen and the decisions in them are recorded, with their options, reasons and who decided, so nobody has to say "record this". The pieces are in the current release; the setup that makes it one step is not.

Planned

Decided, not built

On the roadmap, in the open. Shown here as intent, not as something that exists yet.

Planned

Speed, consistency and flexibility

Across your decisions with your agents: how fast you get from question to decision, how often a new decision agrees with the ones already in place, and how often you change your mind when evidence arrives. Shown side by side, never as one number, never as a ranking. A fast reversal on new evidence reads as a strength.

Planned

With and without Loomtracer, side by side

The same engineering task run twice by a coding agent: once with a hand-kept decisions file, once with Loomtracer. Recorded, reproducible, and the site will say what it shows and no more.

Planned

Two projects, drifting apart

Your agents work several projects, and one replaces a decision another rests on. Today the decision resting on it reads stale, also across linked projects, and "what should I know?" looks in the project it depends on. The drawing marks what is planned: catching a contradiction with no recorded link, and a count of the links that still hold.

Drawn: two lanes drifting apart
  1. 1 · Aligned

    Record idsnever change Every recordhas a version The API roundsprices Cache recordsby id Cart total fromthe sent prices Show pricesas sent rests on rests on rests on rests on API MOBILE APP PLANNED 4 of 4 links between the lanes hold

    Your agents run two lanes, the API and its mobile app. The app’s decisions rest on the API’s in four places. Those links are the alignment: 4 of 4 hold.

  2. 2 · One lane moves

    Record idsnever change superseded Every recordhas a version The API roundsprices Cache recordsby id stale Cart total fromthe sent prices Show pricesas sent Merge duplicates;ids can change rests on rests on rests on rests on replaces API MOBILE APP PLANNED 3 of 4 links between the lanes hold

    The API lane merges duplicate records, replacing "record ids never change". The app’s caching decision rested on it, so it reads stale. 3 of 4 links hold.

  3. 3 · The lanes contradict

    Record idsnever change superseded Every recordhas a version The API roundsprices Cache recordsby id stale Cart total fromthe sent prices Show pricesas sent superseded Merge duplicates;ids can change Round priceson the phone rests on rests on rests on rests on replaces replaces contradicts, no link API MOBILE APP PLANNED 2 of 4 links between the lanes hold PLANNED

    Later the app rounds prices on the phone, replacing "show prices as sent", with no link to the API’s rounding. The lanes now contradict each other, and 2 of 4 links hold. Catching that, and showing the count, are planned.

Start with one decision

Point Claude Code, Codex or Cursor at your self-hosted Loomtracer, as a local binary or in a container.