Local records. Optional processing. Clear limits.
The alpha keeps its core project-context record on your machine. It makes the data path easier to inspect, but it cannot make an agent or computer safe by itself.
Start with the local record.
Termyte stores the work it captures in a local SQLite database. That includes configuration, traces, tasks, observations, memories, context records, and feedback. Local retrieval does not require an embedding API, and telemetry is not enabled by default.
- The record is local by default.
- You can inspect what was captured.
- You can use capture-only mode without provider-backed synthesis.
Processing is a choice.
If you turn on processing, Termyte sends redacted trace-derived content to the provider you chose during setup. Capture-only mode records activity without asking a provider to form observations or memories.
This means “local” does not mean that no data can ever leave the machine. It means the core records are local and provider processing is an explicit part of setup.
What Termyte cannot protect against.
- Malware, malicious local users, or a compromised machine.
- Unsafe actions taken by a coding agent.
- Secrets that heuristic redaction does not recognize.
- Activity from tools or agents that are not connected to Termyte.