Docs

1. Create an account (email, full name, username, password) or log in if you already have one. You'll land straight in the workspace.
2. Write or research in the document area, same as any text editor.
3. When you need to step away, tap Save where my brain is. Add a quick note if you want, or skip it — either way it's instant.
4. Close the tab. Come back whenever — an hour later, or tomorrow.
5. Reopen the workspace. It quietly offers to restore your last save point. Click Restore where I was and you'll see one clear next step first, then where you were.

A save point is a snapshot of where your head is — your goal, what you'd already decided, and what's next — not your files. Your browser already keeps those. What it usually doesn't keep is the reasoning that connected them: why you were reading this, which idea you'd ruled out, what you were about to write next.

When you restore a save point, an AI model reconstructs that reasoning from whatever you gave it (a note, your document, a selection, the page you were on, your other open tabs) and hands you back one concrete next action, plus the context behind it. It marks anything it isn't sure about instead of guessing silently — see the FAQ below on what happens when it's unsure.

The extension lets you create a save point from any web page — not just the workspace — so it works where your reading actually happens, across dozens of open tabs. It is desktop Chrome only; Manifest V3 extensions don't run on mobile browsers at all.

1. In Chrome, go to chrome://extensions.
2. Turn on Developer mode (top right).
3. Click Load unpacked and select the extension's extension/ folder (see the note below if you don't have this project's files).
4. Click the Save Point icon in your toolbar. It opens straight to a small login form.
5. Log in with the same username and password you use on the workspace. No codes, no ids to copy — that's it.

The popup shows exactly which username will own the save. Its Save where my brain is action captures the active tab, any selected text, a short page snippet, and your other open tab titles — plus an optional note — into the same account as your workspace saves. After saving, Open workspace opens that exact point at /workspace. The website and extension keep separate sessions, so their shown usernames must match. If the extension session expires, the popup returns to its login form.

Only the active page is captured by default. Include other open tabs is optional and off for every save; those pages are retained only as links and are not used to invent the current task.

Production defaults to https://savepoint-seven.vercel.app; local development uses http://localhost:4477. If you need to switch, right-click the extension icon → Options and change the Workspace address to match — for example https://savepoint-seven.vercel.app to save into the live deployment instead of a local dev server.

Don't have this project's files? “Load unpacked” needs an actual folder on your computer — Chrome can't install an extension from a link unless it's published on the Chrome Web Store. Ask whoever is running this build for a copy of the extension/ folder, or check whether it's been published to the Web Store yet — if so, install it from there instead and skip the steps above.

What actually gets in the way of using it

Being honest about this matters more than most feature lists, because this build is not on the Chrome Web Store yet — every limitation below is a direct consequence of that, not a design choice:

• School-managed Chromebooks often block it entirely. Most K–12 school IT departments manage student Chromebooks through Google Admin policy, and a common default is disabling Developer Mode and unpacked-extension installs outright. On a locked-down school device, step 2 above (“Turn on Developer mode”) may simply not be an option — the toggle is greyed out or the whole page is blocked. There is no workaround for this from inside the extension; it needs either a Chrome Web Store listing (which admins can allow-list) or an IT exception. This is the single biggest real-world gap for the actual target audience of this product.
• No auto-updates. Because it's not on the Web Store, the extension never updates itself. If the code changes, you have to manually reload it (chrome://extensions → the reload icon on the Save Point card) or re-do “Load unpacked” with the new files.
• Chrome nags about it. Chrome periodically shows a “Disable developer mode extensions” warning banner for any unpacked extension. Dismissing it is safe; it's Chrome being cautious about unsigned code, not a sign anything is wrong.
• Some pages block it from reading anything. Chrome doesn't allow extensions to run on its own internal pages (chrome://), the Chrome Web Store, or a handful of sites with unusually strict content-security policies. On those pages, the popup still opens and still saves — it just captures an empty selection and snippet instead of erroring. If a save from one of these pages looks unusually empty, that's why.
• Chrome (desktop) only, tested. Manifest V3 extensions can sometimes load in other Chromium-based browsers (Edge, Brave), but that's untested here — assume Chrome unless you've verified otherwise yourself.

Browser extensions don't run on any mobile browser — not Android Chrome, not iOS Safari. That's an Apple/Google platform restriction, not something any web app can work around. The same is true on a school Chromebook with Developer Mode disabled (see above). Two real fallbacks exist for both cases:

1. The workspace itself, on your phone

The workspace is a normal responsive website — open it in your phone's browser, sign in, and it works the same as on a laptop, just stacked into one column. What you lose without the extension is automatic page capture: you can't grab the current tab's title, selection, or a snippet with one tap. What you keep is everything else — write a quick note about what you were reading (typed or dictated, using your phone's own voice-to-text keyboard), tap Save where my brain is, and the AI reconstructs from that note the same way it would from anything else.

2. A bookmarklet — the closest thing to the extension, on a phone

A bookmarklet is a bookmark whose address is a small piece of JavaScript instead of a URL — tapping it runs on whatever page you're currently looking at. It needs no app store, no browser extension store, no Developer Mode, and works identically on iOS Safari, Android Chrome, and a locked-down school Chromebook. It captures the same scope as the desktop extension (page title, address, your selection, a short snippet) and hands it to your already-signed-in workspace to confirm and save — it can't save directly, because a bookmarklet runs on someone else's page and has no way to prove who you are on this one.

Save Point only reads what's in front of you at the exact moment you choose to save — the active tab's title and URL, any text you had selected, a short snippet of the page, your other open tab titles, and whatever note you leave. Nothing more. The mobile bookmarklet follows the identical rule.

There is no background monitoring, no continuous screen capture, no browser-history reading, and no keystroke logging. Both the extension and the bookmarklet are save triggers, not a surveillance layer — neither does anything until you tap them.

The one deliberate exception is the workspace document itself: while you're typing there, a plain local draft is kept in your browser's own storage — never sent to the server or the AI — purely so a forgotten save never means losing what you wrote. That same local activity (typing, then going quiet) is also what triggers the occasional “want me to save your place?” offer. It reads only this one document, on this one tab. Not your other tabs, not your browsing history, and nothing runs in the background once you close it.