Documentation Index
Fetch the complete documentation index at: https://docs.termyte.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Why Termyte?
The biggest bottleneck for AI agents today is not reasoning—it’s reliability. Coding agents suffer from Stochastic Looping: the tendency to repeat the same broken command or delete files because they don’t remember what happened 5 minutes ago.The Problem: The Loop of Insanity
When an agent fails, it tries again. Without persistent memory, it often tries the exact same thing or a slightly different version that fails for the same reason.- Repeat Errors: Trying
npm installover and over when a peer dependency is missing. - Destructive Regressions: Accidentally deleting a file, then trying to “fix” it by deleting more.
- Amnesia: Forgetting that a specific command is dangerous for your environment.
The Solution: Persistent Failure Memory
Termyte gives your agents a persistent muscle memory. It doesn’t just store “chats”; it stores a governed ledger of every command and its outcome.1. Stop Repeat Failures
Termyte remembers when an action fails. The next time an agent tries that same approach, Termyte warns it: “This failed with exit code 1 last time. Try a different strategy.” This breaks loops instantly.2. Safety Policies
You can define hard rules for your project. If an agent tries torm -rf / or git push --force on main, Termyte blocks the execution before it hits your terminal.
3. Local-First Redaction
Your secrets should never leave your machine. The Termyte MCP bridge redacts API keys and environment variables locally before recording the action in the cloud ledger.Who is it for?
- Solo Developers: Stop your agent from accidentally trashing your local git state.
- Teams: Build a shared memory of “traps” in your codebase so new agents (and humans) don’t fall into them.
- Production Systems: Run autonomous cleanup or monitoring agents with the confidence that they won’t delete the database.
Quickstart | Core Concepts