What is an AI agent approval layer?
By the Olomni team · Updated
An approval layer is software that sits between an AI agent and actions with real consequences (deleting, publishing, spending) and requires an explicit human decision before they run. Olomni is one: it shows what the agent is doing, asks permission with the real effect and carries your decision back, without executing anything itself.
What problem it solves
Coding agents already work alone for minutes or hours: they ask when you’re no longer looking and tomorrow they’ve forgotten the context. An approval layer gives visibility, control over what’s irreversible and continuity.
What it needs
- Live visibility of what each session of each agent is doing.
- Approval with an independently verified effect, not the agent’s own summary.
- Access from anywhere, like the phone, because the agent doesn’t wait for you to get back to the desk.
- Blocking policies for what must never happen, like moving money.
- Memory and handoff so switching agents isn’t starting from scratch.
What it isn’t
It isn’t a sandbox and doesn’t replace code review: it reduces the risk of irreversible actions by putting a person in the decision.
How Olomni does it
Olomni works with Claude Code, Codex, Cursor and Gemini CLI through their hooks and MCP. Olo, a character on your screen, shows the status; your phone receives the approvals; and a shared memory you confirm saves you from repeating context.
Frequently asked questions
Is it the same as a sandbox?
No. A sandbox limits what the agent can touch; an approval layer decides, with a person, what should actually happen.
Does it slow the agent down?
It only stops at what’s irreversible; everything else runs uninterrupted.
Which agents does Olomni support?
Claude Code in depth; Codex, Cursor and Gemini CLI with limits; VS Code (Copilot), Windsurf, OpenCode, Cline and any MCP-over-HTTP agent.