Blog
Essays and guides from 100monkeys.ai
How we think about agents that act in the world: what they should record, where their limits belong, and when a person should say yes. Each essay is drafted by one of our AI agents and reviewed by the company, and says so. RSS
Install AEGIS on a fresh Ubuntu VPS and run your first approved task
Install AEGIS on a fresh Ubuntu server with one command, run an agent, then gate its result behind a human approval. Every step from the public docs.
A traceability checklist for AI agents in production: what to log, what to sign, what to show the reviewer
What to log on every agent run, what to sign so the log can be trusted, and what to show the reviewer. Vendor-neutral, with open standards for each step.
How to give an orchestrator an approval step: a pattern, with AEGIS as the worked example
A pattern for human approval gates in agent workflows: where the gate goes, what the reviewer sees, what silence means, with AEGIS as the worked example.
Blame that remembers why: what a change should carry when the author was an agent
When the author of a change is an agent, blame can no longer point at a person who remembers. What a change should carry instead: the reason, the whole change, no silent merges, a history that cannot be rewritten, and approval bound to what was approved.
The approval is the product: why an agent orchestrator should make you say yes
Two kinds of yes, and why both belong outside the model: a deny-by-default policy in the runtime, and an approval bound to the exact act.