Operon OS Agenaut docs
Operon OS Agenaut sits between your AI agents and the tools they can touch. You decide what each agent may do on its own. Anything risky waits for your approval, and every step leaves a signed receipt.
- 1. Get an account
- 2. Connect Claude
- 3. Connect another agent
- 4. Put your MCP servers behind Agenaut
- 5. Choose what each agent may do
- 6. Approve or decline a request
- 7. Rules
- 8. The ledger
- 9. Stop an agent
- 10. Practice tools
- 11. How Agenaut protects you
- 12. Help
1. Get an account
Agenaut is in beta, and new accounts need an invite. Ask for one with Request access on agenaut.operonos.com. Once you're in, add a passkey in Settings: approving anything that can't be undone, such as sending a message, asks for it.
2. Connect Claude
- In Claude, open Customize, then Connectors, then + Add, then Add custom connector. If Agenaut is listed in Claude's connector directory, you can add it from there instead.
- Name it Operon OS Agenaut and use this address:
https://mcp.agenaut.operonos.com/mcp - Claude opens Agenaut's sign-in page. Sign in, choose the agent's level (see section 5), and press Connect.
Claude now sees the tools you switched on, under Agenaut's names. When Claude calls one, Agenaut decides: it runs, it waits for you, or it is refused.
When a request waits for you, Claude is told so and should ask you to approve it in Agenaut. After you approve, ask Claude to try again: the same request then runs once.
3. Connect another agent
Any agent that speaks MCP can connect. In Agenaut, open Connect an agent and pick it from the list:
- Agents that sign in (such as ChatGPT and Meta Muse): paste the same address and sign in, as for Claude.
- Agents that take a key: Agenaut gives the agent its own address and key, shown once. The agent sends the key as an
Authorization: Bearerheader.
4. Put your MCP servers behind Agenaut
Agenaut guards the tools of MCP servers you already use. Open Tools in the app:
- Add a server. Give it a name, its address (it must start with
https://) and its key, if it needs one. By default the key is sent as a bearer token; you can name another header, such asX-API-Key. Agenaut keeps the key sealed and sends it only to that server. Your agents never see it. - Review its tools. They arrive switched off. For each one, Agenaut suggests a risk class (read, write, share, send, delete, settings, forwarding or money) from the tool's name and the server's own hints, taking whichever is riskier. Change it if it's wrong.
- Switch on the tools your agents may use. A tool that is switched on is offered to every agent in your account, through Agenaut. Each agent's level still decides what runs on its own.
Agenaut doesn't move money, crypto or other financial assets: a tool classed as money can't be switched on.
For tools that share, send or forward, tell Agenaut which argument names the person who receives it. Without that, every call to the tool waits for you.
Your agents read Agenaut's own name and description for each tool, not the server's. You can read what the server says in Details, write a better description, or use the server's own text if you trust it.
If a server changes a tool after you switched it on, Agenaut switches it off until you look again: press Check for changes on the server. If a server stops offering a tool, it disappears from your agents. You can pause a server, replace its key, or remove it at any time.
5. Choose what each agent may do
| Level | What it may do on its own |
|---|---|
| Observer | Reads only. It can't change, send or share anything. |
| Assistant | Reads and writes. Anything else waits for you. This is the default. |
| Trusted | Like Assistant, and it may send again to people you approved before. A new person still waits for you. |
Whatever the level, these always wait for you: sharing outside your account, sending to someone new, moving money, deleting, changing settings, new forwarding or filter rules, and anything done to more than 10 items at once.
6. Approve or decline a request
A request that waits shows on your Home screen and in the Ledger, on your phone or your computer. You read the whole request before you decide; hidden characters and look-alike addresses are pointed out. Approving money, a send or a delete also asks for your passkey.
By default a request waits 15 minutes. If nobody decides in that time, it closes, and the agent has to ask again.
7. Rules
A rule lets one agent do one thing without asking, with one person or with anyone: for example, "Claude may share with Rahul without asking". Agenaut offers a rule after you approve the same thing twice; you can also add one in My rules. Sending, paying and deleting can never be made automatic.
8. The ledger
Every decision Agenaut makes, and every decision you make, gets a signed receipt in the Ledger. Receipts hold codes and digests, not what was asked, and they can't be quietly changed. You can download everything your account holds from Settings.
9. Stop an agent
Open the agent and press Stop. Every call it makes is refused from then on, and anything it left waiting closes. If an agent asks for too much too quickly, Agenaut pauses it on its own and tells you.
10. Practice tools
Agenaut can also offer a set of practice notes tools: read, add, share, send and delete. They change nothing anywhere. Use them to watch approvals, waiting and receipts work before you switch on real tools.
11. How Agenaut protects you
- Agenaut decides by each tool's risk class, never by what an agent was told.
- An agent never sees a server's key, or a server's own tool descriptions unless you adopt them.
- Agenaut connects only to public https addresses, and doesn't follow redirects.
- A tool you switch off stops at once, even for a request that is already waiting or approved.
- Your sign-in lives in a cookie no web page can read.
To report a security problem, see security.txt.
12. Help
Write to sri@operonos.com. How Agenaut handles your data is in the privacy policy.