The guide
Using Window Memory well
Two weeks later, you reopen the project. You don't re-read your own code. You just say "hi" — and your AI answers: "Last time you were wiring up checkout. Stripe's webhook kept failing because the signature check ran before the body was parsed. Your goal: launch Friday — 2 days left."
You never wrote that down. You never will.
There are two kinds of builders: the one who keeps losing the thread, and the one who ships. This guide is how to be the second kind.
Window Memory remembers your build — every decision, the why behind it, and the things that didn't work — so your AI tool (Claude Code, Cursor, Codex…) never makes you re-explain, and never walks you back into a dead end it already hit. You don't operate it. You just build. A few habits make it compound — and the better you use it, the more it becomes yours.
1. Start with "hi"
There's nothing to set up and nothing to write down — just work in your AI tool as usual. If you've built here before, your memory is already waiting, and it only gets stronger. Every session you work adds to it, and it keeps more than what changed: it saves your intent and your AI's reasoning, side by side. That pairing is the part git can never give you. The more you build, the more powerful — and the more yours — the project's memory becomes.
- • Every session opens with "Last time you …" — a one-line catch-up plus your goal and the time. You never start cold.
- • Before risky moves, your AI is reminded of what already failed — so it doesn't retry the path that broke last week.
- • It captures the why, not just the diff. Git shows what changed; Window Memory remembers why you decided it.
2. Talk to it — and never take it on faith
No commands needed. Your AI pulls memory on its own, but you can summon it in plain language:
- • "What did we try for X last time?" → the past decision and the reason.
- • "Where were we?" → the recent thread.
- • "Did this already fail?" before you commit → it checks past attempts first.
It runs automatically — but you're never asked to trust it blindly. Open the dashboard and see exactly what it captured. Doubt it, doubt it again, and ask it to explain any event in plain language. Automatic capture plus a memory you can audit and interrogate is what makes it safe to rely on.
3. Keep your charter true
After a week or two, Window Memory drafts a charter for your project — its purpose, the current goal, and milestones — and feeds it into every AI session, so your tool stays pointed at what you're actually trying to ship.
Why it matters: building moment to moment, goals blur. Today's fix, next month's plan, and the original idea start to mix, and you drift — polishing the wrong thing, adding what nobody asked for.
- • Check it when you feel scattered. Dashboard → Goals. Is this week's work actually serving the goal? If not, you've drifted.
- • Let it catch you. Window Memory flags when your recent work pulls away from the goal — treat that as "stop and check."
- • When you pivot, update the charter through your AI. Just say: "Our goal changed — update the charter: the goal is now X, drop the old milestone, add this one." Future sessions realign immediately, so past, current, and future goals stop fighting each other.
4. Build with a team
Invite a teammate and your memories merge into one shared build memory — including the failures. A teammate's "tried X, broke because Y" saves the whole team from the same wall, and new members get caught up automatically instead of needing a long handoff. Sharing is on by default for exactly that reason; mark anything sensitive private per-event when you need to.
Free vs Pro
Free runs entirely on your own machine, on one project at a time, with your own AI key — your other projects stay saved but paused (read-only) until you make one active or upgrade. Pro ($15/mo) includes the AI — no key to manage — removes the one-project limit, syncs your memory to every device and mobile, lets you recall across all your projects, and adds team sharing. New accounts get a short Pro trial so you can feel the full thing first. Prove it on one project; go Pro when you're juggling more than one, building across devices, or bringing in a team.
That's the whole craft: build normally, trust the "Last time you …", keep your charter true, and let the failures — yours and your team's — stop everyone from repeating them. That's the builder who ships.