Project memory scope

The idea

A memory can belong to one repository, and only work that names that repository recalls it. The visibility rules do not change.

The problem
Notes about one repository leaked into work on another.
Why it matters
Recall stays relevant to the code the work touches.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Hybrid memory recall

    Recall ranks memories with full-text and trigram search, plus vectors where embeddings exist. It says which arms ran and why vectors are off, and it gives the worker its readable memory as files.

  • Correct once

    When you correct an AI worker once, Crewshal turns the correction into a lesson, and the worker gets that lesson again when later work touches the same part of the code.

    Recorded walkthrough

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.