memex

Deliberately capture what you JUST did as a Memex case — a worked episode (trigger / situation / actions / outcome / lesson) the system derives a reusable procedure from. Use right after finishing a multi-step task, diagnosing a bug, or resolving an incident, or when asked to 'record/log/save how I did this'. Distinct from /remember (auto-routes by shape) and /extract-case (converts existing content) — this is the structured, in-the-moment path.

Resume work from previous /handoff notes. Presents a multi-select list of the most recent handoff summaries, lets the user pick any number of relevant items (or 'load more'), then loads every selected note, summarizes them jointly, and asks what the next steps should be. Use at the start of a fresh session, or when the user says 'pick up where we left off', 'continue', 'what was I working on', 'resume', or 'catch me up on this'.

Tell Memex a surfaced memory was wrong, outdated, or noise. Use whenever you say 'stop suggesting that', 'that's stale / outdated / wrong', 'we removed that', or want a misleading fact to stop surfacing — records a not_helpful outcome on the offending unit(s) and deprioritizes them (the negative-signal loop). NOT for confirming a fix worked (that's a helpful outcome).

Turn a note, a markdown file, or a URL into a Memex case — but only when the content actually contains a reusable how-to / worked episode. Gated: if there's no case in it, files nothing.

Write a technical handoff summary of the current work to Memex — a descriptive, summarizing writeup of what you've been doing, the approach and key decisions, where it stands, and what's next — so you (or another agent) can pick the thread back up later. Use at the end of a workday, when wrapping up an involved conversation, or whenever the user says 'hand this off', 'write up where we are', 'summarize this so I can continue later', or 'I'll come back to this'.

Distill the durable learnings from the current session and save them to Memex, routing each into the right memory layer by shape. Use when the user says 'capture what I learned', 'save the lessons from this session', 'what should we remember from this', or wants the takeaways from the whole conversation kept — as opposed to one named episode (`/case`) or one supplied fact (`/remember`).

Review and resolve Memex memory-hygiene findings — stale facts, near-duplicates, contradictions, orphaned mental models, mis-routed notes. Use when the user says 'lint my memory', 'clean up stale/duplicate memories', 'triage the maintenance ledger', or wants to work through the linter's pending findings. The agent explains each finding and, with your go-ahead, resolves or dismisses it.

Search Memex long-term memory. Returns facts, notes, and entities matching the query.

Save information to Memex long-term memory. Routes how-tos/worked-episodes to a case, preferences/conventions to KV, or facts/decisions to a note.

Pull the content of a local file or a web page (and its assets) into Memex as a note — verbatim or summarized. Use when the user says 'ingest this file/page', 'save this URL to memory', 'add this document to Memex', or hands you a path or link to capture. This stores the raw content as a note (extraction runs server-side) — NOT a gated how-to case (`/extract-case`), and NOT a single shape-routed fact (`/remember`).

Recall the step-by-step how-to for a task from Memex's procedural plane. Use whenever you ask 'how do we X?', 'how do I X?', 'what's our process/checklist for X?' (deploy, release, rotate creds, migrate) and want the concrete steps — NOT the general approach (that's /strategy). Reach for this before improvising a multi-step task you may have done before.

Recall the cross-procedure strategy for a verb — Memex's top procedural tier: the general approach/philosophy that spans the individual procedures for a scope + verb. Use when you ask 'what's our approach to X?', 'how do we think about X?', 'the strategy behind X' and want the overall stance, NOT the step-by-step how-to (that's /procedure).