Shroud Bridge

Small desktop app (Tauri) that runs a local OpenAI-compatible → Shroud proxy in-process (no Node.js on the user’s machine). Rust implementation: src-tauri/src/llm_proxy.rs. The 1claw proxy CLI mirrors this behavior in packages/cli/src/commands/proxy.ts in the 1claw monorepo.

• License: MIT (see LICENSE)
• Requirements: A 1Claw agent with Shroud enabled and ocv_ credentials (or uuid:ocv_…). Network access to your Vault API and Shroud URLs.

Public repository

Source of truth: github.com/1clawAI/shroud-bridge.

Clone standalone

git clone https://github.com/1clawAI/shroud-bridge.git
cd shroud-bridge
npm install
npm run dev

Production bundle:

npm run build

Installers appear under src-tauri/target/release/bundle/ (.app / .dmg on macOS, .msi / .exe on Windows, .deb / .AppImage on Linux depending on Tauri defaults).

1claw monorepo (submodule)

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 dev

CI

The monorepo runs .github/workflows/shroud-bridge.yml on Ubuntu, Windows, and macOS when packages/shroud-bridge/ changes.

Security notes

• 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.

Limitations (v0.1)

• Parity: When changing proxy behavior, update src-tauri/src/llm_proxy.rs and the CLI proxy command together (or add shared contract tests).

Docs

• IDE & Shroud setup
• Shroud guide