ClawTrust
2.3k Downloads
Overview
Provides a local HTTP sync server that enables secure, two-way synchronization of markdown notes and related files between a Clawdbot/OpenClaw workspace and an Obsidian vault (via the `obsidian-openclaw` Obsidian plugin).
Key Advantages
1.Enables true two-way sync between Obsidian and the Clawdbot/OpenClaw workspace, not just one-off imports or exports.
2.Designed with clear security boundaries: explicit allowed subdirectories, path traversal protection, and mandatory bearer-token auth.
3.Simple, well-documented configuration via environment variables (port, bind address, workspace root, allowed paths, token).
4.Integrates directly with a companion Obsidian plugin that adds chat, file actions, and audit logging, providing a cohesive workflow.
5.Supports running as a persistent background service (systemd user service) and recommended secure remote exposure via Tailscale.
Use Cases
- Researchers, writers, or knowledge workers who want their Obsidian notes to stay synchronized with an OpenClaw/Clawdbot agent’s workspace for context-aware chat and tooling.
- Developers using Obsidian as a project knowledge base who want their agent to read and modify project notes safely within constrained subdirectories.
- Teams or power users running a self-hosted OpenClaw agent that needs continuous access to a curated subset of an Obsidian vault (e.g., `notes` and `memory`).
- Users who want to issue file operations (create, edit, delete notes) through conversational interaction with an agent while keeping the underlying files in sync with Obsidian.
- People needing a controllable, network-exposed sync endpoint (e.g., via Tailscale) that can be run as a service and integrated into their existing infrastructure.
Evaluation Scores
7.7
/ 10
Reliability
7.2
Functionality
8.7
Usability
6.5
Safety
8.2
Performance
7.8
Compatibility
7.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: linux-x64LLM: anthropic/claude-opus-4.6
**Quick judgement:** This skill is a focused, well-scoped sync server that cleanly bridges an OpenClaw/Clawdbot workspace and an Obsidian vault. It appears thoughtfully designed for secure, two-way markdown sync and is especially valuable if you already use Obsidian and want your agent to operate on real vault files instead of copies.
**What it does well**
- Provides a clear HTTP API (`/sync/status`, `/sync/list`, `/sync/read`, `/sync/write`) tailored to markdown file synchronization.
- Enforces security boundaries: explicit `SYNC_ALLOWED_PATHS`, path traversal blocking, and mandatory `Authorization: Bearer <token>`.
- Encourages safe deployment patterns (bind to localhost and expose via Tailscale; systemd user service example for persistence).
- Integrates with a dedicated Obsidian plugin (`obsidian-openclaw`) that adds chat, file actions, and audit logging, giving a complete workflow rather than a bare sync backend.
**Risks and limitations**
- Requires self-hosting and some DevOps comfort (Node runtime, environment configuration, systemd/Tailscale); non-technical users may struggle.
- Security depends heavily on correct configuration of `SYNC_TOKEN`, `SYNC_ALLOWED_PATHS`, and network exposure; misconfiguration could unintentionally expose notes or the agent workspace.
- Reliability characteristics (error handling, conflict resolution robustness, large-vault performance) are not fully documented; heavy or complex sync scenarios may require testing.
**Recommended scenarios**
- You actively use Obsidian and want your OpenClaw agent to read/write your notes safely, with ongoing two-way sync.
- You’re comfortable running a small Node-based HTTP service and optionally exposing it securely via Tailscale or similar.
- You want a conversational interface (via the Obsidian plugin) to manage notes while maintaining your Obsidian vault as the source of truth.
Comments (0)
No comments yet. Be the first!