Using your Vault

Lampway gives Claude memory. This page is about how to use it — the day-to-day rhythm that turns a chat tool into a continuous practice.

The core idea: three short prompts bookend every Claude conversation so the next one picks up where you left off. The Keeper handles state continuity across sessions. You handle the work.

This page assumes you've installed Lampway and run /introduce. If you haven't, start at Help for setup — then come back.

The session loop

Every Claude conversation has the same shape: open, work, close. Three prompts make that loop coherent across sessions.

Kickoff — opening a new conversation

Starting cold. Two prompts that recover context from where you left off:

• "Keeper, what were we working on?" — the Keeper surfaces the most recent project, the last session's handoff note, and any open items. Best when you're not sure where you left off.
• "Let's continue work on [project]" — scoped to a specific project. The Keeper pulls that project's most recent note and durable Memory entries.

During — capture as you go

Two modes. Passive: the Keeper saves what you tell it to as the conversation flows. "Remember that I prefer Postgres over MySQL" writes a feedback Memory entry. "Save that decision about the auth flow" writes a project Memory entry. No special syntax — natural language.

Active: when a thought is too important to lose but you don't want to derail the conversation, run /capture-thought. It's a Built-in Skill that prompts for a quick capture and writes either a Memory entry or a Tier 3 note depending on whether the thought is a durable fact or an exploratory one.

Wrap-up — closing the session

The most important prompt in the loop. When the conversation is winding down, type:

"Keeper, wrap this session up."

The Keeper then:

1. Summarizes 2-4 bullets of what you decided or learned this session — surfaced for you to confirm or edit before anything is written.
2. Asks which project this conversation belongs to (Chat mode only — Cowork and Code infer from the open folder).
3. Writes a Tier 3 note to <vault>/<project>/notes/YYYY-MM-DD-<topic>.md with the narrative — what happened, decisions made, open items, what's next.
4. Offers durable Memory entries derived from the session. You pick which to save.
5. Saves the chosen entries via keeper_remember.
6. Closes with the kickoff hook: "Next time, ask me what we were working on and I'll pick this up."

The Tier 3 note is the handoff document; the Memory entries are the durable facts that outlive the note. Both matter, for different reasons. The note lets the next session pick up context cold. The Memory entries are what the Keeper consults later when you ask abstract questions — "what do I prefer?", "what have I decided about X?"

Cadences — Skills that overlay the loop

The session loop covers the moment-to-moment. Four more Built-in Skills overlay it at daily, weekly, and event scales. None are required — the session loop is the floor — but they're how you build the practice into a habit.

The Vault on disk

Everything the Keeper writes lands on your machine as plain Markdown. You can browse it anytime, with any editor:

• Memory entries at <vault>/00-meta/memory/ — one Markdown file per entry, each with type frontmatter
• Tier 3 notes at <vault>/<project>/notes/ (project-scoped) or <vault>/notes/ (vault-root, for project-agnostic captures)
• The Memory Index at <vault>/00-meta/memory/MEMORY.md — auto-maintained by Lampway, lists every Memory entry with a one-line hook

Sync the Vault folder with iCloud, OneDrive, Dropbox, or git — your choice. The Vault is yours; Lampway is the curator.

Forgot a prompt or need to revisit setup? Help covers the install flow, the three-layer customization stack, and the Vault Memory vs Auto Memory distinction.