The you that persists.
Models change.
You don't.

What sthayi guarantees

before you install anything from the web

how it works

memory bill of rights

Ten commitments grounded in the architecture, license, and documented product behavior.

terms used on this page

Precise words, defined once, so the rest of the page can use them.

MIT licence

The most permissive licence in common use. Copy it, change it, ship it inside something you sell, no permission needed. It carries exactly one condition — see the attribution entry.

attribution

MIT's single requirement: keep the copyright line and licence text with the code when you redistribute it, including inside a closed-source or commercial product. You don't owe us payment, credit in your UI, or a copy of your changes — just don't strip the notice. That's the whole obligation.

no CLA

No contributor licence agreement: you sign nothing to contribute, and we acquire no special rights over the code that contributors don't have.

local-first

sthayi runs and stores on your own machine and needs no server we operate — there is no hosted sthayi service and no sthayi account. Core use works offline. Commands you explicitly run, such as the oracle pass or sthayi qualify, contact the provider you select.

telemetry

Usage data sent back to a vendor. There is none here — no analytics, no crash reports, no counts.

SQLite

A database kept in local files. sthayi's store is SQLite-backed under ~/.sthayi/ by default. Use the README's backup and export guidance rather than copying the live database while it is in use.

MCP

Model Context Protocol — the connector standard AI tools already use to reach external tools. It is how a wired client reads and writes your memory without per-app custom work.

stdio

The pipes a program uses to talk to another program on the same machine. sthayi's MCP server uses stdio by default, so the client-to-sthayi link stays local — which is also why a website cannot use it. An advanced optional transport serves the same tools over authenticated loopback HTTP on 127.0.0.1, still as a local process.

wired client

A supported AI client whose config points at your local sthayi MCP server. Memory a wired client stores through sthayi becomes available to other wired clients; a wired client does not capture every conversation on its own.

keyless core

Storing, searching, writing, serving memory and the local consolidation pass need no API key for core use and no paid AI subscription. The oracle pass and sthayi qualify are the only operations that contact a provider, on a key you supply.

bring your own key

The optional oracle pass and sthayi qualify run on your own provider account, so the cost and the data path are yours to control. Provider keys are stored locally and used only to call the provider you chose. Core use needs no key at all.

episodic / semantic / procedural

The three memory types: something that happened, a durable fact, and a way you like things done.

proposal

A candidate memory awaiting your confirmation. Imports and agents write proposals, never facts.

consolidation

The local, keyless tidy-up pass: merge exact and near-duplicate memories, apply decay. Runs on your machine with no key and no model.

oracle

The optional bring-your-own-model memory-consolidation pass — not prediction, not fortune-telling, not a general assistant. It sends bounded, masked batches of memory to the provider you select and proposes merges, contradictions, archives and distillations. sthayi validates and journals every proposal before applying it.

sthayi qualify

A check that your chosen provider and prompt pack behave as expected. It contacts that provider, but sends shipped synthetic fixtures rather than your memories.

hash-chained journal

Each log entry carries a fingerprint of the previous one, so altering old history breaks the chain visibly. Append-only, hash-chained, and tamper-evident.

append-only

Entries are added, never edited or deleted. Rollback covers consolidation batches by writing compensating entries rather than erasing the originals.

masking / pseudonym

Detected secrets and supported personal identifiers are masked to stable pseudonyms such as EMAIL_01 at write time, so context survives without the real value. Detection is best-effort and does not claim to catch every possible secret.

adapter / importer

An adapter connects a supported AI client; an importer teaches sthayi to read a history format. Both are documented interfaces.

unwire

Disconnecting sthayi from your AI clients. If the config is untouched since wiring, it is restored byte-for-byte from the setup backup; if you have edited it since, unwire removes only sthayi's entry and preserves your other changes.

build with us