Approve what Openclaw does before it does it.

Permission Slip is an open-source approval layer for Openclaw. Every action Openclaw wants to take — sending emails, merging PRs, booking flights — goes through you first. Nothing happens without your say-so.

┌──────────┐         ┌─────────────────┐         ┌──────────────┐
│ Openclaw │ ──────→ │ Permission Slip │ ──────→ │   Gmail,     │
│          │ ←────── │   (approval     │ ←────── │   Stripe,    │
└──────────┘         │    layer)       │         │   GitHub,    │
                     └─────────────────┘         │   Slack…     │
                           │                     └──────────────┘
                           │ push notification
                           ▼
                     ┌───────────┐
                     │  You      │
                     │  (approve │
                     │  / deny)  │
                     └───────────┘

🚀 Try it now

permissionslip.dev — hosted, no setup required.

Get the iPhone app to approve requests on the go.

Or self-host it on Docker, Fly.io, or bare metal. Even runs on a Raspberry Pi 5 in under 30 minutes.

✨ Why Permission Slip?

You want Openclaw to book flights, send emails, and merge PRs. But you can't trust it with full access to your accounts. Your options today:

• 😬 Give Openclaw your passwords — it can do anything, anytime, with no oversight
• 😩 Do everything manually — defeats the purpose of having Openclaw
• 🤞 Hope it asks nicely — it could hallucinate, misunderstand, or get compromised

Permission Slip solves this with a secure proxy + human-in-the-loop approval model. Openclaw submits structured, schema-validated actions — never arbitrary API calls. Nothing executes without your explicit sign-off.

Beta status & how we build

The project is in beta: behavior, APIs, and connectors will keep evolving, and you should expect rough edges.

The architecture and product direction are designed by humans; the codebase is largely written with AI-assisted development (with human review and iteration layered on top). Treat the implementation as fast-moving software, not a formally verified system while it is in beta. If this ever gets more enough use, I'll update some processes, get a formal security review done, etc. Still just exploring at the moment.

Want to run, build, or change the code? Start with the Developer guide — local setup, production builds, testing, and tech stack — then CONTRIBUTING.md for workflow and standards.

🔑 Key Features

• 🛡️ Action-based security — Openclaw submits structured actions, not raw API calls
• 🔔 Per-request approval — push notifications with human-readable summaries
• ✅ Standing approvals — pre-authorize trusted, repetitive actions with constraints
• 🔐 Cryptographic identity — Ed25519 key pairs for tamper-proof request signing
• 🙈 Zero credential exposure — Openclaw never sees your API keys or passwords
• 📋 Full audit trail — every request, approval, and execution logged
• 🔌 OAuth 2.0 connections — Google, Microsoft, Dropbox, and custom providers; PKCE where required; tokens encrypted at rest with automatic refresh
• 📱 iPhone app — approve on the go from your phone
• 🏠 Self-hostable — your data, your infrastructure
• 📦 Single binary deployment — Go server with embedded React frontend

🔌 Connector Health

Connectors are being tested incrementally during the beta; maturity varies by integration.

Have you tested a connector? Open an issue to let us know!

📚 Documentation

👩‍💻 For developers & contributors

Developer guide — clone the repo, local dev servers, production make build, observability env vars, testing commands, and tech stack overview.

CONTRIBUTING.md — issue workflow, code standards, migrations, and pull request expectations.

📖 Getting Started

• Self-Hosted Deployment — Docker, Fly.io, bare metal
• Raspberry Pi Quickstart — up and running in 30 minutes
• Architecture — system diagrams and component overview
• SPEC.md — protocol design, security model, and full spec

🔌 Integrations & Connectors

• Openclaw Integration Guide — how Openclaw connects to Permission Slip
• Creating Connectors — build new built-in connectors
• Custom Connectors — add connectors from external Git repos
• Community Connectors — third-party connector directory

🔒 Protocol Reference

• Terminology — core concepts and definitions
• Authentication — agent identity and request signing
• API Reference — complete endpoint documentation
• Notifications — push notification and webhook delivery
• OpenAPI Spec — machine-readable API definition

🚀 Deployment

• Fly.io Deployment — Dockerfile, fly.toml, DNS setup
• Mobile Builds — EAS builds, OTA updates, App Store submission

🧪 Contributing & Testing

• Developer guide — local dev, builds, tests, stack
• CONTRIBUTING.md — development workflow and code standards
• Integration Testing — end-to-end test strategy
• Manual Testing: Agent Registration — invite/registration flow walkthrough

🤝 Contributing

Contributions are welcome! For setup and commands, see the Developer guide; for process and standards, see CONTRIBUTING.md. Browse open issues to find something to work on.

📜 License

Permission Slip is licensed under the Apache License 2.0. Built by SuperSuit — questions or feedback welcome at supersuit.tech.

👥 Contributors

Thanks to everyone who has contributed!

_{Made with contrib.rocks.}