CLAWSOLATOR ALPHABeta release planned · License under considerationRead what is verified
XERXES SI / SECURITY ENGINEERING

NVIDIA OpenShell and Clawsolator: Complementary Security Layers

OpenShell enforces what the agent may do inside its runtime. XMAN targets the surrounding human and operational process. Here is the integration hypothesis—and what must be proven before shipping.

Independent engineering commentary by XERXES SI · Updated November 1, 2026 · Claims separated from roadmap

Architecture fit

Different layers, different questions

QuestionOpenShellXMAN / Clawsolator direction
Can a process read, write, connect, or call a tool?Enforce external runtime policies.Coordinate compatible sandboxes and independently gate specified host actions.
Who can grant permission?Gateway/policy approvals and operator administration.Named requests, approval histories and operator review workflow.
What if an agent runs away?Contain process/network activity according to policy.Resource budgets, timeout and job scheduling controls under development/implementation review.
Can we rebuild evidence after a restart?Runtime audit and policy records.Durable request state, recovery pathways and attributable logs—verify per release.
Are they already integrated?No. Future compatibility is being evaluated; no shipped OpenShell integration is claimed.

Why the pairing is interesting

SysOp Clawsolator lobster avatar
SysOp

“If OpenShell already does the sandbox and the egress rules, why would I want XMAN?”

Security Officer Clawsolator lobster avatar
Security Officer

“Because an organization also needs operator-owned change management, recovery, accountability, agent assignment and resource plans. But we should integrate—not duplicate enforcement.”

Scope note: NVIDIA already documents strong external enforcement and auditing. Any claim that OpenShell lacks approval, rootless Podman, or network control would be inaccurate.

Integration gates before making a public promise

Proof of compatibility

Install OpenShell and XMAN in a lab, verify rootless lifecycle behavior and document supported APIs.

Policy conflict mapping

Make explicit which system is authoritative for process, network, filesystem and human approval gates.

Audit linking

Correlate request IDs and OpenShell policy decisions without creating a second source of truth.

Failure drills

Test restart, denial, policy changes, offline operation and resource exhaustion, then publish redacted results.

Strong claims deserve strong evidence.

Inspect the controls, verify the boundaries, and ask what happens after a failure—not merely before it.

Explore the security lattice →Read the architecture →

CANONICAL TRUST BOUNDARY

Agents request. XMAN decides. Operators authorize exceptional host work.

Each registered agent uses the authenticated requester API through the trusted Gateway bridge. The XMAN management daemon governs policy, resource admission and durable outcomes through its private Unix-socket interface. The operator API is separate; the master coordinates but does not become the operator. The future SysOp and Security Officer daemons would be separate, permissioned services, not current Alpha functionality.