Open-source tutorials
Get enclawed running on your real problem
Each tutorial below takes you from a fresh enclawed-oss install to a working agentic-AI scenario on real data — in roughly one afternoon. The four scenarios cover the surfaces most operators ask about first: a personal-productivity agent, an inbound-channel triage bot, a private RAG over PDFs, and a code-review agent that posts on a GitHub PR. Every scenario uses the same install line, the same ~/.openclaw/openclaw.json config, and the same enclawed audit verify chain check at the end.
Pick the one closest to what you actually need to ship. The other three are deliberately small variations on the same skeleton, so once you have one working the rest are easy.
Virtual secretary — now a one-line install demo
The Gmail + Calendar secretary moved out of the long-form tutorial track and into the one-line install demo at enclawed.com/enclawed-apps/secretary. Same agent, same security properties; the install is now under fifteen minutes and runs as a background service on macOS, Linux, and Windows.
Customer-support triage on Telegram
Read inbound tickets from a Telegram channel, classify them, draft a first response, and let the operator approve or deny each one before send. Uses the bundled telegram-llm extension, the HITL gate, and the DLP scanner for PII in drafts.
Document research — private RAG over a PDF corpus
Ingest a folder of PDFs into a local LanceDB index, then answer questions with citations. The egress allowlist is set to the empty set: zero internet access for the agent, zero data egress from your corpus. Audit log proves which document each answer cited.
Code-review agent on a GitHub PR
Pull a PR diff, run lint suggestions, and post a single review comment. The bundled mcp-github bridge wires GitHub’s first-party MCP server (github/github-mcp-server) into the admission gate, egress allowlist, and audit chain.
These tutorials cover enclawed-oss — the MIT-licensed open-source core. Same install line, same config file, same audit chain throughout. Running the enclawed-enclaved flavor? Your licensed build ships with its own tutorials for the enclaved-only features — and what you learn here still applies, since your ~/.openclaw/openclaw.json and audit log carry over unchanged when you upgrade the binary.