ClawForge – MDM for AI assistants (governance for OpenClaw)

Name: ClawForge – MDM for AI assistants (governance for OpenClaw)
Availability: InStock
Author: clawforge

by clawforge·Feb 24, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●●●BangerSolve My ProblemSlick

MDM for local AI agents—audit trail and killswitch before OpenClaw agents go rogue.

Strengths

•Edge-enforced policies with fail-safe design prevent unauthorized tool execution
•Audit trail covers all tool calls and sessions, supporting regulatory compliance
•Seamless SSO integration with OIDC reduces friction for enterprise adoption

Weaknesses

•Depends on OpenClaw adoption (single-vendor lock-in, emerging ecosystem)
•Limited documentation on policy composition and edge case failure modes

Post Description

AI assistants are going local.

Tools like OpenClaw let employees run AI agents directly on their machines — with file access, shell execution, web fetch, custom skills, etc.

That’s powerful.

But for enterprises, it creates a new problem:

• No visibility • No policy enforcement • No audit trail • No kill switch • No control

We built ClawForge, an open-source control plane for OpenClaw.

Think of it like MDM — but for AI assistants.

ClawForge gives organizations: • Org-wide tool allow/deny policies • Skill approval workflow • Audit logs for tool calls & sessions • Heartbeat monitoring • Emergency kill switch • SSO/OIDC auth

Architecture:

OpenClaw instance (employee machine) → ClawForge plugin → Control plane (API) → Admin console

Policies are enforced at the edge (client-side), not server-side blocking.

If the control plane is unreachable, it fails secure.

Repo: https://github.com/ClawForgeAI/clawforge

Would love feedback from folks working on AI agents, DevTools, or enterprise security.