Permaura for OpenClaw · On your server, around the clock
Give OpenClaw permission, not your keys.
OpenClaw runs agents for you on heartbeats and schedules, which is exactly when nobody is watching. Permaura keeps every key out of the OpenClaw Gateway, makes the call itself, and holds anything that sends, posts or spends until you say yes on your phone.
It's free on your own computer: the gateway runs from the terminal on macOS, Linux and Windows, or as the Mac app, or let Permaura host it. Approvals reach your iPhone and Apple Watch, your Mac, or the console in any browser.
Try itAn OpenClaw agent is tidying up and picked the wrong repo.
OpenClaw wants to delete a repository on GitHub
github.repos.delete · acme/payments-api
Agent says
You asked me to clean up unused repos, and this one has had no commits in 90 days.
Approve it or deny it. Nothing real happens here.
Set it up
Connect OpenClaw in a few minutes.
OpenClaw connects to tool servers natively over HTTP, so there is no bridge to install: one entry in its config and one code from the console. OpenClaw usually runs on a server, so your gateway needs a public address that server can reach: a hosted gateway has one, and one you run yourself gets one from remote access. Written against OpenClaw 2026.10.4.
A gateway on your own computer gets a public address from remote access; a hosted gateway has one from the start.
- 1
Mint a code. In the console, open Agents, then Connect agent, type OpenClaw as the agent name, and copy the MCP server URL and the code (the part after Bearer). The code is single-use and lives 15 minutes.
- 2
Store the code where OpenClaw keeps secrets. On the machine running the OpenClaw Gateway, run this, paste the code at its hidden prompt, then restart the OpenClaw Gateway so it has the new variable.
On the OpenClaw machine(umask 077 && touch ~/.openclaw/.env && chmod 600 ~/.openclaw/.env && IFS= read -rs T && printf 'PERMAURA_AGENT_TOKEN=%s\n' "$T" >> ~/.openclaw/.env) - 3
Add Permaura under mcp.servers in ~/.openclaw/openclaw.json. Keep transport set to streamable-http; without it OpenClaw assumes a different transport. The OpenClaw Gateway applies the change without a restart.
~/.openclaw/openclaw.json{ mcp: { servers: { permaura: { url: "https://your-gateway.permaura.app/mcp", transport: "streamable-http", headers: { Authorization: "Bearer ${PERMAURA_AGENT_TOKEN}", }, }, }, }, } - 4
Or do it from a terminal with the OpenClaw Gateway stopped. The single quotes keep the variable reference out of your shell's hands, so OpenClaw saves the reference and never the code.
From a terminalopenclaw mcp set permaura '{"url":"https://your-gateway.permaura.app/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${PERMAURA_AGENT_TOKEN}"}}' - 5
Connect within the code's 15 minutes: with the OpenClaw Gateway stopped, run openclaw mcp doctor permaura --probe, or start a new chat session. The agent appears as Pending on the Agents page. Approve it there, and on your phone if a paired device confirms agent approvals.
- 6
Grant it something and run the whole loop once with something harmless, such as opening a test issue. The call answers at once with a pending status, the request lands on your phone, and the agent collects the result on its next heartbeat.
The address and the code on this page are the examples from the docs. The console's Connect agent dialog fills in your own gateway's address and a live code, and names the exact menu or file for the client you pick. Source: The docs page Connect OpenClaw.
What you'd use it for
Hand OpenClaw the job. Keep the last word.
Three jobs people hand to OpenClaw most, and the moment each one asks you. That is the default. You choose what needs approval.
Gmail
Work the support inbox
It reads and searches the mailbox on every heartbeat, sorts out what needs a person, and drafts the replies.
Asks you first: sending a reply, or trashing a message.
GitHub
Keep the repos moving
It reads the issues, pull requests and commits across your repos and writes up what it finds.
Asks you first: opening an issue or a pull request, and merging.
Reddit
Watch the subreddit
It reads the posts and comments, searches, and reads the account's inbox.
Asks you first: posting, replying, editing or deleting, and sending a private message.
What Permaura can and cannot enforce
It guards the door it stands at, and says so.
Permaura governs what passes through it, and it has only the keys you have moved into it. Anything your assistant can reach another way, it reaches without asking.
Permaura governs
Every call made through a Permaura connection.
The key stays on the gateway, which adds it on the way out and scrubs it from the result. The assistant gets an answer, never the login.
What runs on its own, and what waits for you.
Reading runs on its own by default. Sending, spending, deleting and publishing start switched off and ask you first, app by app, and you can change any of it.
Who may say yes, and the record of it.
A held call waits for a tap on your iPhone, Apple Watch or Mac, or in the console, signed by that device. Every decision goes into a record you can check, and a pause from your phone stops every assistant at once.
Permaura does not govern
OpenClaw's own tools: its shell and exec, its file tools, its browser, and whatever a skill does. Those run inside OpenClaw with the access OpenClaw gives them, and its tool policy and sandbox are where you limit them.
The chat channels OpenClaw is connected to directly, the model provider keys it thinks with, and any other MCP server in its config.
Any key the agent can already reach. If a GitHub token is still in OpenClaw's environment, an agent with a shell can use it with curl and never touch Permaura. Putting a service behind Permaura means moving its key: add the connection, take the key out of OpenClaw, and rotate it, since it has already lived in that environment and in any backup of it.
The Permaura token itself. It is a credential OpenClaw holds, and anything that can read it can act as that agent, within that agent's grants. Removing the agent on the Agents page ends it at once.
Questions
What people ask before they connect OpenClaw.
What happens if my assistant is tricked?
Its requests through Permaura still have to pass your rules. An action requiring approval waits for you; a denied action is blocked. An allowed action can still be misused, and data from an allowed read reaches the assistant. Permaura does not control its local shell, separate tools or credentials stored elsewhere.
Where do my passwords live?
The credentials you add stay with the gateway that runs your connections: on your computer for a local gateway, or on Permaura's servers for a hosted gateway. Permaura uses them to make requests on your assistant's behalf. Hosted means trusting Permaura to operate the service holding those credentials.
Can I turn it off?
You can pause access through Permaura or remove a connection. That stops access through the gateway. If an assistant also has a direct key or another connection to the app, you need to revoke that access separately.
What does it cost?
Running the gateway on your computer is free. Your computer needs to stay on for it to run. You can bring your own tunnel for remote access. Paid plans add hosting, a managed public address and team features. Plans are not priced per assistant or per call; hosted usage is subject to fair-use limits.
Give OpenClaw its first safe connection tonight.
It's free on your own computer. Connect one app, say what needs a yes, and answer the first request from your iPhone, Apple Watch or Mac.