Capture and recall memory

Crosshead keeps recent working state for the next session. You can also save something on purpose or search older records when a task needs them.

On this page

Check what carried forward

A completed turn can save a checkpoint containing your request and the agent’s findings. Crosshead calls this hot memory. The next connected session can get a short selection of relevant recent checkpoints, including the problem you were solving and the next action.

crosshead memory hot --scope all

This shows a profile’s saved working memory across scopes. A session receives a smaller selection for its workspace. Add --json to inspect the structured output. If a finding appears in the CLI but your agent misses it, ask the agent to state what it knows about the specific task and inspect the receiving session.

Before stopping halfway through a task, ask for a short wrap-up that includes the exact decision, a rejected approach and why it failed, the verification actually performed, and the next unfinished step. A specific final answer gives the hook something useful to capture.

Save a fact or correction deliberately

When you learn something worth reusing, tell the agent what to remember and why. In a connected session with the remember capability, you can ask it to use that capability explicitly.

Use Crosshead to remember this as a correction for this repository. The fixture generator expects UTC timestamps. Local timestamps make the date-boundary cases intermittent. Keep this scoped to the fixture generator.

Ask the agent to report the result of the save, then inspect it separately. An explicit remember can become eligible for recent hot recall and request promotion to warm memory. Saving a long-term entry uses credits if the hosted write succeeds. Run crosshead memory hot to inspect recent capture and crosshead memory warm to check for an existing long-term entry. Keep project-wide rules in your repository’s instructions as well.

Find a decision from older work

Warm memory holds longer-lived facts, patterns, and corrections. Cold archives hold saved session logs when archiving is enabled and funded. An ordinary checkpoint does not automatically make the full session searchable later.

crosshead billing status
crosshead memory warm
crosshead memory search "CSV import blank optional columns" --top-k 5

Hosted search uses credits. Try the decision’s subject and one distinctive detail, such as a filename or error message. Review the matching record, then give the current agent the specific part it needs. Paid context packs and archive results are available on demand. The automatic brief continues to use verified hot memory.

Running out of credits leaves free working memory available. See current pricing and funding options before using paid operations.

Correct stale memory

If a recalled finding conflicts with current instructions or code, check the source. Tell the agent exactly which old claim changed and what replaces it. When a correction needs to endure, update the project file that governs the behavior and save a scoped correction. A new checkpoint can carry the correction forward without erasing the earlier record.