A memory layer. Honest about where the data goes.
Termyte is a local memory layer, not a sandbox and not a runtime safety product. Everything it stores stays on your machine in a single SQLite file.
What stays local
- Every trace, observation, memory, and embedding — all in your SQLite database.
- The embeddings model runs on your machine via ONNX. No embedding API key required.
- No telemetry, no analytics, no data ever leaving your computer.
- The database file is portable: copy it, sync it, or leave it where it is.
The one optional network call
Memory synthesis can reuse the LLM plan you already pay for — for example, the Claude or Codex plan you're subscribed to. That call goes to the same provider you're already using, not a separate Termyte service. You can turn synthesis off entirely and still capture traces and run keyword search.
Outside the scope
- Sandbox isolation or guaranteed runtime safety. Termyte remembers; it does not contain.
- Protection against malicious attackers, malware, or kernel-level compromise.
- Validation of everything your agent does — only what is captured through hooks becomes a trace.
Bounded by default
Background synthesis is capped: 50 invocations per day and an estimated $0.50 per day, configurable via environment variables. A per-batch timeout and a 50-trace batch cap keep the synthesis from eating your quota or running forever.