Skip to content

Persistent memory
for AI agents.
No re-explaining.

A local memory layer that captures context once and recalls it inside every AI tool you use.

Get Early AccessOur Approach
  • PERSISTENT MEMORY
  • CITED BY DEFAULT
  • MCP-NATIVE
  • LOCAL-FIRST
  • ZERO LOCK-IN
The Problem

Your AI forgets you.
Every tool. Every session.

001002003004
LIVE SCAN-85°
  1. 001
    CONTEXT LOSS

    Every session starts from zero.

    Yesterday's chat. Last week's decision. Last quarter's architecture call. The next AI session knows nothing about any of it.

  2. 002
    VENDOR SILOS

    Memory is trapped per-tool.

    ChatGPT remembers inside ChatGPT. Cursor remembers inside Cursor. The walls are deliberate, and they cost you the moment you switch.

  3. 003
    UNVERIFIABLE

    No source. No date. No ID.

    "As we discussed" comes back without a citation. You're trusting that the model isn't inventing the memory you're about to act on.

  4. 004
    LOCK-IN

    Your context lives on their disk.

    Whatever the platform decides about retention, training, or pricing — the accumulated context is hostage. Switch vendors, climb the hill again.

Introducing memwork

A complete memory layer that runs on your machine. No vendor memory. No prompt-stuffing. No re-explaining.

VENDOR MEMORYYOUR MACHINEYOUR SOURCESCHATS · MEETINGS · NOTESmemwork· INITIALIZING ·SQLITEVECMCPYOUR TOOLSCLAUDE · CURSOR · ZEDTELEMETRY
SCAN: vendor-memory dependency
LOCAL · OFFLINE-OK · NO TELEMETRY
Persistent

Never repeat yourself.

New chat. New tool. New laptop. Your context is already there, with the source attached, before the model speaks.

  1. FRICTIONLESS

    Capture without thinking.

    Save mid-stream from any AI tool, any meeting, any note. memwork keeps the original text and the source — you never have to copy-paste between tabs again.

  2. PRIVATE

    Cut the silos.

    Memories live in a SQLite file you own. No cloud sync. No vendor memory store. The only network call is the embedding API, and you choose the provider.

  3. FAST

    Skip the re-explain.

    Recall happens in-process, in milliseconds. Every result returns with source name, date, and ID — so the next AI session starts with what you already know.

Our Approach

Recall beats re-explanation.

memwork is a closed loop — capture, index, recall — engineered together for one outcome: the next AI session already knows what you decided.

CAPTURE THROUGHPUT

BENCH · MW-001

Snippets ingested per second · M-series MacBook

memwork

0/s

Manual paste

0/30s

Local indexing pipeline runs without leaving your process.

DELTA30,000×
Capabilities

Your context, unbroken.

[ 01 ]

Understands your sources.

Builds a connected graph of where each memory came from, how recent it is, and which others it relates to — so recall surfaces the cluster, not just the single hit.

[ 02 ]

Cites every recall.

Source name, date, and stable memory ID surface on every result. Verify before you trust. Click through to the original any time.

[ 03 ]

Strategizes ranking.

Hybrid scoring: vector similarity, lexical match, recency decay, source weight. Tunable per workflow without rebuilding the index.

[ 04 ]

Captures any AI session.

MCP for editors, CLI for scripts, manual paste for the moments in between. The schema enforces a sourceId on every write — there is no path that forgets.

[ 05 ]

Isolates user scopes.

Single-user, single-device by design in v1. No cross-user query path. Sharing is a separate product with a separate trust model — and we'll ship one good thing first.

[ 06 ]

Runs at full speed.

SQLite + sqlite-vec, in-process. Vector search and lexical search compose in the same query plan. Cold start is one file open. Backups are cp.

LATENCY

<60ms

p50 hybrid recall

PRIVACY

Local

SQLite on your disk

COST / RECALL

$0

your machine, your tokens

VENDOR LOCK

0

MIT, MCP, swappable

Engineered Intelligence

Built for the mid-task.

memwork://localhost · offline
NEURAL ENGINEMW-001LOCAL OPS

LOCAL STORAGE

SQLITE + SQLITE-VEC · ONE FILE

INFERENCE

OPENAI EMBEDDINGS · SWAPPABLE

CONTEXT INDEX

VECTOR + LEXICAL HYBRID

MCP SERVER

STDIO TRANSPORT · ONE BINARY

VALIDATED

ZOD AT EVERY BOUNDARY

OPINIONATED

SOURCED BY DEFAULT

Early Access

We're inviting engineers to install it on real workflows and tell us what's broken before it ships.

0ENGINEERS · WAITINGv1 · QUEUED
Get Early Access ↵

one email when v1 ships · no drip · no scarcity timer

FAQ

Frequently asked questions.

MEMWORK · v1 · 2026

Your AI is about to remember.

Every session.Every tool.Every laptop.

Remembered.

0ENGINEERS WAITINGNO CREDIT CARDNO SCARCITY TIMERNO TELEMETRY