Your machine · your data · nobody else involved. WebLLM runs in-browser. OAuth tokens stay on device.
b botler
T0 sovereign

What do you want me to remember?

Five commands. One prompt. Your memory · your machine · nobody else involved.

botler type a command · or just talk
T0 · grep mode · no AI needed
Recent · last 5
Nothing yet
Tell me what to remember.

the trust model

I run on your device. Memory lives in your browser's IndexedDB. WebLLM runs locally — no API call unless you opt in. OAuth tokens stay client-side. If you trust your hard drive with your documents, you can trust me with your memory. Same storage, same access, same security.

All memory

Everything I've remembered for you · daily summaries · projects · people · raw notes.

findor filter by tag · date · person
Daily summaries
Projects
People
Raw notes

Inbox

Drop a file · paste a URL · pull email. I'll process it · summarise it · log it in memory.

📥
Drop files here · or click to pick
PDF · text · images · audio (m4a / wav) · URLs
pasteURL · text · email body
Processed (last 10)

Integrations

OAuth handles every connection. Tokens stay on your device. Read-only by default · I never write to your accounts.

about OAuth scopes

I ask for the minimum read-only scope each service supports. Gmail metadata + message bodies. Calendar event list. Drive file listing only. I never request "send mail" or "manage calendar" scopes. Your token goes from Google to your browser to my IndexedDB. Nobody else sees it. You can revoke any time in your Google security settings.

Settings

One file's worth of config · all stored client-side · export at any time.

you
ai
T2 is recommended once · downloads ~2GB on first use · then runs offline forever.
journal
data
cannot be undone · export first