You know that thing — the contractor's name, the customer-service workaround, the explanation a friend wrote you about how their refinance went — that you read in an email two years ago and can almost remember? You search your inbox for the obvious word. You search again with a different word. You give up and ask the question again, knowing you've already answered it once.
Most of what we've learned over the past decade lives in our inboxes. Not in the chatty parts; in the good parts — a long thread where a real expert explained something, a PDF an old colleague sent that you actually read, a vendor's reply that solved a problem the first time. Email is a great delivery vehicle and a terrible archive.
A vault that holds the useful slices of your inbox — and an agent that can actually search across them — fixes most of the friction. The point isn't to copy your whole inbox over. The point is to capture the parts that turn out to matter. (For the broader version of this practice — voice notes, screenshots, photos all lumped in too — Turn Casual Captures Into a Searchable Life Archive is the matching guide.)
A capture habit that takes ten seconds
In Docapybara, the unit of capture is a page. The friction of "should I save this?" needs to be near zero or you won't do it.
The habit that works is small. When an email is genuinely useful — a real explanation, a recommendation worth keeping, a thread you'll want to refer back to — forward it to your vault, or paste the body onto a new page, with a one-line title at the top. "Mortgage refinance — Sara's explanation of the 5/1 ARM math." That's it. The agent does the indexing later.
Pages nest with no depth limit, OneNote-style, so a parent page called Inbox capture can branch by topic — Money, Home, Health, Work, Friends — or stay flat. Whichever shape you'll actually keep up with.
For the threads where the useful part is buried in a long back-and-forth, paste only the message that matters and a one-line note about the context. The agent doesn't need the full thread; you don't either.
Attachments that become searchable, not just stored
The most valuable emails often aren't the message — they're the attachment. A PDF report a friend forwarded. A scanned tax document. A spreadsheet of the comparison you did three years ago. A medical document from a portal.
Attachments dropped on a page convert automatically. PDFs become searchable markdown via the agent's PDF pipeline, so the actual content of the document — names, numbers, dates, sections — is indexable text rather than locked inside a flat file.
The result is that the agent can answer questions across the attachments, not just the message bodies. "What did the inspection report on our last house say about the roof?" The answer comes back with a quote from the actual PDF and a link to the page.
For email-delivered receipts and statements (the kind that stack up in a Receipts folder you never reread), an inline database makes the pile useful instead of just present. The :::database::: directive lets a small spreadsheet live alongside whatever prose context you want — vendor, amount, date, category, link to the source page. The agent can update it. "Add the receipt from this email — vendor [X], amount [Y], category equipment."
Forward-to-vault as the muscle memory
For most people, the bottleneck isn't deciding what to save — it's the friction of saving it. The habit that compounds is forwarding (or pasting) to the vault as a near-reflex.
A good rule of thumb: if you've ever forwarded an email to yourself "to remember later," it belongs in the vault. Self-forwarding is your past self admitting the inbox isn't where you'll find it next time.
For threads you're actively in, capture at the moment of resolution. The customer-service exchange that finally fixed the problem — copy the working answer onto a page titled with the problem, before the thread sinks into the archive. The friend who finally answered your question about a particular doctor — capture the recommendation onto a People & recommendations page.
The agent reads across years of capture in one query
The reason capture is worth the small effort is what becomes possible later. With even a few months of decent capture, the agent can answer questions that span the inbox.
"Pull every recommendation I've gotten for plumbers, with who recommended them and any notes." The list comes back, grounded in the actual emails you saved.
"What did our accountant say last year about the home-office deduction?" The agent finds the page where you saved the thread and quotes the relevant paragraphs.
"I remember someone explained dental insurance to me clearly — find that thread." You get the page back, even if you can't remember who sent it or which year.
The reason this works is that the vault stores plain markdown — not a tree of structured blocks. Markdown is the format AI is fastest at. When you ask the agent to read across hundreds of pages, it reads them as text and returns answers; it doesn't have to walk a block graph.
Replies and follow-ups the agent can draft from your archive
Once you've captured a few thousand words of context — past decisions, recommendations, your own past replies on similar topics — the agent can draft new replies that sound like you, because they're grounded in things you actually wrote.
"I got an email from a friend asking how I handled the kitchen renovation budget. Look at the renovation pages I have, draft a reply that summarizes what worked and what we wish we'd done differently." The draft comes back, you adjust the parts that don't sound right, you send it. You didn't summarize a year of renovation from memory; the vault did.
For frequent question-answerers — people who keep getting asked the same kinds of things by friends, family, or coworkers — a Stock answers page becomes useful over time. The thoughtful version of the explanation you've now written four times. The agent can pull from it and adapt to the new sender. (For an in-depth take on drafting against your own material rather than blank pages, see How to Draft Emails, Proposals, and Newsletters Inside Your Notes App.)
A few specific captures worth being deliberate about
Some categories of email reward a deliberate capture habit more than others.
Recommendations from people you trust. Restaurants, doctors, contractors, products, services. These get sent to you in passing and disappear. A Recommendations page (or an inline database with name, type, source, status) turns the disappearing into the searchable.
Long explanations from experts. The friend in finance who walked you through the mortgage decision. The cousin in medicine who explained what a particular test result actually meant. The colleague who finally taught you how a particular system works. These are gold; they don't survive in your inbox.
Customer-service workarounds. The reply from the airline that finally got the refund processed. The exact magic words that unlocked a refund or got an order corrected. These compound across a lifetime of consumer interactions.
Decisions and rationale. The email where you made the case for a job change, a school decision, a financial move. The reply where you explained the reasoning. These are the kinds of artifacts your future self will want, and your past self has already written.
Receipts for things you actually own. Big purchases, warranties, equipment with serial numbers. These are the ones the warranty company will eventually ask about; saving them once means you have them forever.
A complementary habit some people find useful: a People page or database with one row per person you stay in touch with — what they do, what you've talked about recently, kids' names, any context worth carrying into the next conversation. Built up over years from emails and notes, it stops you having to ask "remind me what your son's studying again?" (For the underlying capture practice, The Capture Habit: Remembering the Things That Actually Matter is the home base.)
A starter shape for the inbox-to-vault transition
If you're starting from "I've never captured anything from email before," this is the shape we'd suggest:
- A Captured from email parent page — branch by topic if you want, or keep it flat for the first month and see what categories emerge.
- A Recommendations database — one row per recommendation. Restaurants, services, products, doctors. The single highest-leverage capture habit for most people.
- A People page — context for the people you actually want to stay in touch with.
- A Receipts & warranties database for the purchases you'd be sad to lose.
- A Stock answers page if you find yourself writing the same explanation more than once.
That's it. Don't try to import your inbox. Don't try to be exhaustive. The point is the next useful email — when it arrives, it lands somewhere it'll still be findable in three years.
The point isn't to make email-archiving a hobby. It's that the small amount of capture you do means the next time you almost-remember something, the agent can finish the sentence for you. The recommendation, the explanation, the workaround, the receipt — all of it becomes one searchable surface instead of a folder of search-resistant threads.
Try Docapybara free — start by forwarding three emails this week that you'd be sad to lose, and see how different the next search feels when the answer is on a page instead of in an inbox.