Pick up where you left off

Every recipe ends by offering you a STATE.md block: a short, plain file that holds your goals, decisions and next steps, and nothing that identifies you.

The STATE.md file

It is plain text. Save it anywhere. To resume, paste it into a new chat together with the same recipe prompt and say "Resume from this state." It works in any AI tool, so you are never locked in.

It is built to hold no identifiers: no names, account numbers, SIN or SSN, passwords or addresses. If one slips in, delete that line before you save the file.

# STATE: <thread title>

- thread: <thread-id>
- last_updated: <YYYY-MM-DD>

## Goals

- <what I am trying to get out of this recipe>

## Facts I chose to share

Ranges and rough descriptions only. No names, account numbers, government ID numbers, passwords, or addresses.

- <fact>

## Decisions made

- <YYYY-MM-DD>: <decision, and the reason in a few words>

## Next steps

- [ ] <action> (add "by <date>" only when there is a real date)

## Open questions for an expert

- <question> (for: <accountant, financial planner, lawyer, doctor, IT technician, or other>)

## How to resume

Paste this whole file into a new chat, together with the same recipe prompt, and say: "Resume from this state."

Where to keep it

Choose by how comfortable you are with tools, not by how serious the topic is. Read the security note for your option before you store anything about money or health.

Level Where Trade-off
No setup Claude Projects, ChatGPT Projects, or similar Easiest. Your data sits with the AI provider.
Some comfort A notes app, an Obsidian vault, Notion, or a Drive folder of STATE.md files Readable and portable. Privacy depends on the app.
Technical A local folder under git, optionally SQLite for structured data Private and versioned. Backups are on you.
Very technical Supabase or a self-hosted database Enables automations. You are responsible for securing it.

No setup: a project in your AI app

This suits you if you want to start today and already use an AI app.

  1. Create a project named “Lifemaxxer” in the AI app you already use, such as Claude Projects or ChatGPT Projects.
  2. Start each recipe as a chat inside that project.
  3. When a recipe ends, save the STATE.md block as a file in the project.

To resume, open the project and say “Resume from the state file for this recipe.”

Security note: Your data sits with the AI provider. Check the settings for chat retention and model training, do not share the project, and think twice before using this level for detailed money or health facts.

Some comfort: notes app or a folder of files

This suits you if you already keep notes and like files you can read and move.

  1. Make one folder called lifemaxxer.
  2. Save one file per recipe, named after the recipe, for example find-money.STATE.md.
  3. Keep the folder in a notes app, an Obsidian vault, Notion or a Drive folder.

To resume, paste the file into a new chat along with the recipe prompt.

Security note: Privacy depends on the app. A local notes app or Obsidian vault stays on your device. Notion and Drive hold it on their servers. Check who else can open the folder, such as shared family accounts or shared drives, and lock your device.

Technical: a local folder under git

This suits you if you are at home in a terminal and want a private history of every change.

  1. Create the repository:

    mkdir -p ~/lifemaxxer && cd ~/lifemaxxer && git init
  2. Make one folder per recipe, each holding its own STATE.md.

  3. After each session, save a snapshot:

    git add -A && git commit -m "find-money: session 2"
  4. Optionally keep tabular data, such as a subscription list or a home inventory, in a SQLite file beside it.

To resume, paste that recipe’s STATE.md into a new chat.

Security note: This is private and versioned, and backups are on you. Turn on full-disk encryption (FileVault on macOS, BitLocker on Windows), keep at least one backup on another device, and never push this repository to a public remote.

Very technical: your own database

This suits you if you want automations, such as reminders before renewal dates.

  1. Create a Supabase project or a self-hosted Postgres database.
  2. Add one table for states: recipe id, updated date and the Markdown text.
  3. Turn on row level security before you add any data.
  4. Give an agent a key that can only read and write that table.

To resume, have the agent fetch the latest row for the recipe and paste it into the chat.

Security note: You are the security team. Keep service keys out of prompts, chats and client code, rotate them, turn on multi-factor sign-in, and back the database up. If any of that sounds unfamiliar, the folder under git is the better choice.