All apps

Where Was I

For every project you left halfway

Pick up any project like you never left.

Where Was I reads your files, notes and commits, then hands you a two-minute briefing and your first three actions.

Where you were · Night Library grant

Halfway through section 3, Budget justification. You stopped mid-sentence:

"The remaining 40% of the budget will cover"

And since then: the deadline moved a week earlier.

Twenty minutes of "where was I?"Every time you reopen an old project. Most people give up before they find the thread.

2 minto get your head back in

3 actionsso you start, not scroll

Honest diffof what moved while you were away

Your projects

Which one are you coming back to?

Three sample projects with real-looking folders. In the app you connect a folder, a notes app or a git repo.

Parked projects

Reading

Reading 9 files

Night Library grant

2 min read

Since you left

What changed in 23 days

The honest version: not just what you'd like to hear. Things that changed, things that went stale, and things still missing.

AUDIO BRIEFING

Night Library grant

Tap play. Two minutes, made for the walk to your desk.

0:00 / 2:00

Chapters

Pause note

Leaving for a while? Leave yourself a note.

Thirty seconds now saves twenty minutes later. Your next briefing starts with your own words.

Captured automatically

Where I stopped The very next step What's worrying me Nudge me to come back

Where this goes

Never lose the thread again.

Most of us carry ten half-finished things. The cost of coming back to each one is the reason they stay half-finished. In three years Where Was I wants to be the memory layer for everything you're making.

Year 1

The briefing. Connect a folder, a repo or a notes app. Get a two-minute briefing, an audio version, an honest diff and three first actions. Pause notes when you leave.

Year 2

Hand-offs. The same briefing for someone else: a co-founder, a contractor, a colleague covering your leave. "Brief Amaka on the grant" in one tap.

Year 3

A project memory. Every decision and its reason, searchable across years: "why did we rent the van?" An agent can pick up the next action for you when it's safe to.

North star

Minutes from opening a project to the first real action. Today it's 20 to 40. Target: under 5.

Blueprint

Why this is new

Search tools (Spotlight, Drive search, GitHub search) find a file when you already know what to look for. Note apps and "recent files" lists show what you touched, not what you were thinking. Nothing reads your own recent notes, files and commits to rebuild your context: the last thing you did, the next step you had in mind, the decisions you made and why, and what moved while you were gone.

The data it runs on

The user's project folder, notes or repo: a local folder or a Google Drive or Dropbox folder (via their official APIs with read-only scope), a notes export (Markdown, Apple Notes or Notion export), or a git repo (log, diffs, branches, open issues through the GitHub API).
Change detection: file modified times, document revision history where the API offers it, git commits since the last visit, and new emails or files dropped into the folder.
Limits and gaps: the thinking that never got written down is invisible, scanned PDFs need OCR, and very large folders must be sampled (most recent 200 files, plus anything named notes, todo or readme).
Fallback: the pause note. When the user parks a project, their own 3 lines become the spine of the next briefing, and the app says plainly which parts are inferred and which came from them.

1. The mission

Make returning to any project cost two minutes instead of an afternoon. Rebuild your own context for you, honestly, and hand you the first three actions.

2. Why people can't resist it

The bookmark moment. Seeing your own half-finished sentence quoted back is instantly grounding.
Guilt relief. Abandoned projects feel heavy. A clear first action under 10 minutes makes starting feel safe.
The honest diff. Finding out the deadline moved before it bites you builds deep trust.

3. How it works for real

Index. Read file names, modified dates and text from the folder or repo. Embeddings from a small embedding model rank what matters most.
Find the edge. Plain code finds the last edited spot (cursor position, last commit, last unchecked to-do) and any unfinished sentence.
Summarise. A fast cheap model (Gemini Flash or DeepSeek via OpenRouter) condenses each file into facts with sources. A frontier LLM (Claude or GPT) writes the briefing: last action, next step, open questions, decisions with reasons, first 3 actions, each linked to its source file.
Diff. Compare the snapshot from the last visit (or the pause note) with now: new files, edits by others, expired dates, and numbers that no longer add up.
Audio. A TTS voice (for example an ElevenLabs or OpenAI voice) reads a 2-minute script with chapters.
Pause. When leaving, auto-capture open files and the last edit, plus 3 short lines from the user.

4. Cost per use

About $0.05 per briefing: roughly $0.01 for file condensing with a cheap model, $0.03 for the frontier briefing, $0.01 for 2 minutes of TTS.
Free: 3 projects, 5 briefings a month, text only. Paid ($7 a month): unlimited projects and briefings, audio, honest diff with email and calendar sources, hand-off briefings.

5. Growth loop

Hand-off briefings are shared with co-founders, contractors and teammates, who see the "made with Where Was I" footer and want it for their own projects. Freelancers send clients a "where the project is" briefing instead of a status call.

6. Risks and guardrails

Privacy: read-only access, folder-level consent, processing deletable at any time. No training on user files.
Hallucinated context: every claim links to its source file and line. Inferred items are labelled "inferred".
Secrets in repos: env files and keys are skipped by pattern and never sent to a model.
Over-trust: the diff lists what it could not check (for example, emails outside the folder).

7. MVP build order

Local folder plus git reader that lists the last 50 changes with dates.
Briefing prompt with sources: last action, next step, open questions, decisions, first 3 actions.
Pause note capture and snapshot, so the next visit can diff.
Honest diff of files, dates and numbers since the snapshot.
Audio briefing with chapters.