Skip to main content

Security and privacy

Treat the database as sensitive

Captured events can contain prompts, commands, file paths, tool arguments, tool results, and final responses. Do not commit or share the SQLite database casually.

Redaction

Before persistence, Termyte checks structured secret-like keys and common text patterns such as private keys, bearer tokens, JWTs, GitHub tokens, AWS access keys, and API-key assignments. It stores whether redaction was applied and which rule matched. Redaction is based on known keys and text patterns. It is a safety net, not a guarantee. Unusual credentials or sensitive business data may remain. Termyte is not a secret scanner or a sandbox.

Provider calls

Setup explains when captured content can leave the machine. Memory processing uses the selected Claude Code, Codex, or OpenCode service through a non-interactive CLI invocation, or calls an OpenAI-compatible endpoint. Redaction runs before trace-derived content enters that path. Local embeddings run on the machine, although model files may be downloaded first.

Local services

The Viewer binds to the local machine by default. The MCP server communicates over stdin and stdout rather than opening a port.

Recovery is not backup

Durable jobs, leases, retries, and replay protection help Termyte survive interrupted processing. They do not replace a backup of the database.