Something caught your attention? By morning, it is a finished page
Join the waiting list Already have an account? Log inA library of your interests
The topic that pulled you in stops dying in a bookmark
You send a link with one tap — that is the whole of your part. No formatting, tagging, filing, or remembering. In the morning, you read a finished page: a summary, the source, and links to what you already know. Then you move through the whole night’s work like stories — one insight per screen.
invite only
A base that grows on its own — and keeps itself honest
It is
- Your library of interests. Every link that pulled you in becomes a page with a summary and a source — instead of a bookmark you never open again.
- Knowledge that files itself. A new page finds its own place among the ones you already have. You do not build a structure or invent tags.
- A base that does not stand still. We return to old pages, add connections, and flag facts that stopped being true instead of quietly leaving them in your base as current.
It is not
- A notebook where everything dies. What you send does not stay a raw link in a list. It gets a summary, a source, and a place in the whole. Return to a topic a month later and it is richer than you left it.
- An assistant that guesses. A claim without a source does not enter your base. Citation and provenance are the condition, not decoration.
- A finished agent chat. That part is on the way — the backend returns
501today. See the full status.
What happens while you are not looking
Send
You share a link from your phone or type a note. It lands in
Inbox/ — offline too: it waits in a queue and
goes out when you are back in range.
Ingest
A timer picks up whatever is in the inbox and turns it into pages: a summary, entities, and concepts. Every change goes in as a commit to your vault’s repository.
Tending
A separate pass returns to old pages, adds connections between them, and flags facts that stopped being true. Your base does not stay frozen on the day you wrote it.
Quality gate
A sentence without a source does not get through. A smaller base you can trust beats a bigger one you have to double-check.
In the morning, read it like stories
The brief is not a wall of text you have to scroll through. On your phone, you get one insight per screen, and the card moves on by itself after a reading time calculated from its length.
- Hold and the clock waits. A finger on the screen pauses the timer. It resumes where it stopped, not from the beginning. You can turn the timer off too.
- The bar at the bottom is the card index. You see how much is left, tap a segment to jump to that card, or swipe sideways for another day.
- A background from what you are reading. It is an image from the cited page when the publisher makes one available; otherwise, you see a texture for your area — health, technology, or trading.
- “Do you remember…?” — your base asks, not only grows. One card returns to an old page as a question. Answer I know, Let go, or Later, and the next brief knows what not to ask again.
- It reads offline. A brief that has already downloaded works on the subway, images included.
The format stays yours
- Plain text files, not a closed format. Your base is Markdown, so you can download a full copy at any time and open it in any text editor. Treat that as insurance: you do not have to use it, but nobody holds your data hostage.
- You do not set anything up. We run the backend and the worker during testing. There is no server to stand up or key to paste, and tending runs around the clock without your computer. Transport and backups are encrypted.
- Identity is verified by the backend, not just the edge. A signed token from the login gateway is checked server-side. Your vault follows from your identity, never from a URL parameter. Household vaults are isolated.
- The app works offline. Whatever is already downloaded reads without a network; new items wait in a queue on your phone.
---
tags: [memory, agents]
aliases: [Agent memory]
---
## What we know
The vector index is **derived** —
the .md files remain the source of truth.
Search follows meaning, not spelling:
[[Semantics]], [[MCP]].
## Sources
- [[S - Claude Code]] · 2026-07-24
- https://example.org/paper · 2026-07-19
A graph, not a list
A page links not only by its exact filename, but also by title and alias, regardless of case. That recovers connections which do not exist in a plain wikilink graph.
Clusters are found by label propagation — deterministically, so the same graph gives the same split every time you open it. Colour follows the cluster, not the folder, so you see the areas you actually read about.
- nodes
- 117
- links
- 522
- clusters
- 14
How it feels in your hand
- BriefMorning stories — one insight per screen, moving on by themselves (see above).
- SearchBy name and by content, across the whole base. ⌘K on desktop.
- BrowseTODO, DONE, Inbox, and Wiki as a file tree — the same tree you see on disk.
- GraphYour whole base as a graph, with clusters and a colouring switch.
- MemorySearch by meaning through a vector index, plus a readable digest of what the agents remember.
- SendA link or note in two taps; offline it waits in a queue on your phone.
Chat is deliberately not on this list — it is not ready.
What works and what is on the way
This list is here so you do not have to take our word for it. We take the status from the repository, not from plans.
Works 6 features
- Sending from your phone and an offline queue From the app on every platform, including Android’s system share sheet. Offline, an item waits in a queue on your phone.
- Morning brief as stories — one card per screen The worker writes it every night. On a phone, the progress bar sits below, holding pauses the clock, and tapping a segment jumps to a card. A source image appears when the publisher provides one; otherwise, you see an area texture. On a large screen, the brief is a card list.
- Search and offline use (PWA) Installs from the browser on iOS, Android, macOS, and Windows.
- Knowledge graph with clusters Linking by title and alias, with deterministic clusters.
- Semantic memory (vector index, multilingual model) The index refreshes on a schedule and is separate for every vault.
- Invite-only access, vault isolation, and owner panel In production. An invitation creates the vault on first sign-in.
On the way 5 features
- “Send to Keepino” shortcut on iOS (share sheet) The installer is in the app, the generator works, and the login gateway lets the file through without signing in. One thing remains: the public URL still serves an unsigned version, while iOS 15 and later install signed shortcuts only.
- Agent chat over your base
The endpoint returns
501today. The end state is read-only, using your key. - File encryption on the server (a separate key per vault) A separate key for every vault, kept off the server, so a disk copy is useless without it. Today, transport and backups are encrypted.
- Off-server backups The scripts are ready and waiting for a chosen storage provider. The vault is a git repository, so its history exists from day one.
- Native iOS shell (instead of the PWA) Automated builds reach App Store Connect and are in closed testing. The shell loads the app from keepino.app, so app changes do not wait for a new build. The newest build also puts Keepino in the system share sheet with its own icon and no shortcut. Public access remains browser installation (PWA).
Invite only
There is no sign-up. There is a list.
Leave your address and we will send an invitation when there is room. Without an invitation, an email address will not create a base — and that is how it stays, because behind every base is a machine working for you overnight.