Persistent project memory for coding agents

Your agent forgets.
Calythe doesn't.

Calythe writes your project’s decisions, messages, and file history to one local SQLite file—so the next session starts where the last one ended.

01  Built for projects that outlive a single context window.

THE DIFFERENCE

A context window
isn’t a memory.

A NEW SESSION

Starts cold.

  • Decisions need repeating
  • History lives across chats and files
  • Changing models breaks continuity

WITH CALYTHE.

Starts informed.

  • Decisions stay with the project
  • Relevant history is retrieved on demand
  • The same memory works across models

RECALL

The second session
shouldn’t feel like the first.

Monday
You

“Add session storage. Pick an approach and note why.”

Calyx

“Wrote sessions.py using UUID keys. Recorded the reasoning.”

Quit · new machine · different model
Thursday
You

“Why did you structure it that way?”

Calyx

“Counter IDs were guessable, so they were out. Expiry logic buys nothing when a process restart clears memory anyway. UUIDs in a plain dict were the smallest thing that met both.”

Nothing about Thursday was in the model’s context. Calyx found the decision in the project’s local memory file and sent the relevant part to the model.

HOW IT WORKS

One file. Three steps.

01

Record

Calythe appends messages, file versions, and the reasoning behind decisions as you work.

02

Retrieve

Before an answer, it searches that history and selects the parts that answer the current question.

03

Continue

Connect your API key, pick a model, and continue the same project without starting its memory over.

LOSSLESS MEMORY

The project is the source of truth.

Calythe keeps the underlying messages, file versions, and decisions—not a flattened summary. Each project has one append-only SQLite file on your disk.

DB
calythe.dbProject memory · local SQLite
↳
Messages, file versions, decisions
↳
Portable between machines and models

No account. No Calythe server. Your project history never leaves your machine.

USE CASES

For work that
takes more than one session.

01

Long-running builds

Resume a feature days later without re-explaining the system you already built.

02

Hard decisions

Ask why an approach was chosen and retrieve the trade-off that made it the right call.

03

Model handoffs

Keep the project history when you connect a different model through your own API key.

FOR EMBEDDED

Memory that stays
close to the work.

Calythe keeps its record in the project folder, as a plain SQLite file. That makes the memory portable, inspectable, and contained to the work it belongs to.

One project. One local history. No separate workspace to maintain.

MEASURED SO FAR

Less context.
More continuity.

681

tokens to answer a question about a decision from an earlier session.

−41%

input tokens per turn with prompt caching warm.

0

bytes of project history stored off the machine.

SAFETY, BEFORE AUTONOMY

Memory should be useful, not careless.

Calythe is in development. What works today is deliberately scoped: one project folder, visible writes, and checks before a change is made.

  • Diff before every write
  • Backup before every overwrite
  • Secrets refused for reads as well as writes
  • Scoped to one folder

CALYTHE. / DEVELOPMENT LOG

What’s
changing.

A quiet record of what Calythe is building, testing, and learning as persistent project memory takes shape.

NOW

Project memory, on disk.

Messages, file versions, and decision notes are written to one local SQLite file per project. That file stays portable between machines and models.

LOCAL SQLITEPROJECT HISTORY
NOW

Answers begin with retrieval.

Before a model answers a project question, Calythe searches the project’s own history and provides the relevant context instead of replaying every session.

CONTEXT RETRIEVALLOWER INPUT
IN DEVELOPMENT

One history. Any model.

Calythe is being built so the same project memory can travel with your work when you connect a different model through your own API key.

MODEL PORTABILITYYOUR API KEY

STAY CLOSE

One email
when there’s
something to say.

One email when it ships, nothing else.