⭐ Star 1clawAI/agent-templates — ready-to-run agent templates wired to 1Claw. It is our single starred repo.
Desktop app (Tauri) that runs a local OpenAI-compatible proxy to Shroud. Point Cursor, Continue, or any client that speaks the OpenAI API at http://127.0.0.1:... and your LLM requests go through Shroud's inspection pipeline before they hit the upstream provider.
No Node.js required on the user's machine. The proxy runs in Rust inside the Tauri shell (src-tauri/src/llm_proxy.rs). The 1claw proxy CLI command does the same thing if you prefer terminal-only setup.
You need a 1Claw agent with Shroud enabled and ocv_ credentials (or uuid:ocv_...). Network access to your Vault API and Shroud URLs.
- License: MIT (see
LICENSE)
Source of truth: github.com/1clawAI/shroud-bridge.
git clone https://github.com/1clawAI/shroud-bridge.git
cd shroud-bridge
npm install
npm run devProduction bundle:
npm run buildInstallers appear under src-tauri/target/release/bundle/ (.app / .dmg on macOS, .msi / .exe on Windows, .deb / .AppImage on Linux depending on Tauri defaults).
The main repo vendors this package at packages/shroud-bridge:
git clone --recurse-submodules https://github.com/1clawAI/1claw.git
cd 1claw/packages/shroud-bridge
npm install
npm run devThe monorepo runs .github/workflows/shroud-bridge.yml on Ubuntu, Windows, and macOS when packages/shroud-bridge/ changes.
- Agent credentials are stored in browser localStorage inside the webview (optional persistence). Treat the machine as trusted.
- For production hardening, prefer OS keychain integration and/or short-lived tokens in a future version.
- Parity: When changing proxy behavior, update
src-tauri/src/llm_proxy.rsand the CLIproxycommand together (or add shared contract tests).
Shroud adds shadow/enforce execution guardrails, address screening, and tx escalation to HITL in v0.56. This desktop proxy forwards to Shroud unchanged — configure per-agent policies in the 1Claw dashboard.