What is Mentu?

Mentu is a runtime for work you don't want to babysit.

A lot of useful automation takes hours. A data audit. A batch of lookups across tools. A research pass that reads, checks, writes, and checks again. You want to start it and come back later. The problem is that most tools aren't trustworthy over that long, so you end up sitting and watching, and the work stops being automation at all.

Mentu's job is to make long, unattended work safe enough to actually leave alone.

What you build with it

Three things live on top of mentu:

Sequences. A sequence is a series of steps the runtime works through in order. Each step is handed to a model along with access to the rest of the system. Sequences are what you use when the work has shape: do this, then that, then verify, then ship.

Scripts. A script is a TypeScript program that runs inside a sandbox. Scripts read from the vault, query CIR, trigger sequences, and call external tools. Use scripts when the work is tighter and you want code-level control.

Schedules. A schedule fires a sequence or a script at a given time or on a given interval. Schedules come with circuit breakers and cooldowns, so when a run fails repeatedly, the system backs off instead of looping forever.

What keeps it safe while you're away

Three things. Nothing fancy.

1. Trust is measured, not claimed. The runtime judges the work by what actually happened: did the build pass, did the test run, did the file get written. Agents don't get to grade themselves.

2. Evidence outlasts the run. Everything the system learns is written to a local store called CIR, with a timestamp, a confidence score, and a source. You can always look back and see what the runtime believed, when, and why.

3. Failures stop at clean lines. If a step fails, the runtime stops at the next natural boundary, not mid-execution. The work so far is preserved. Nothing is retroactively wiped.

These are the three properties that let a six-hour run come back to you with a result you can actually use.

What's inside

Mentu is made of five parts that compose with each other:

• CIR. The local knowledge store. Every observation, every claim, every contradiction lives here.
• Vault. Secure credential storage, backed by the macOS Keychain.
• Temporals. Cron-style scheduling with built-in resilience.
• Sequences. Multi-step orchestration for shaped work.
• Scripts. TypeScript programs running in an isolated sandbox.

The CLI (mentu) is the front door. Everything else routes through it.

Where to go next

• What is CIR? The local knowledge store at the heart of mentu.
• Architecture How the pieces fit together.
• Installation Install mentu and set up your environment.
• Quick Start Run your first script in a couple of minutes.