From bopen-tools
Reference for ClawNet CLI internals: vault architecture using SecureEnclaveProvider, ORDFS content fetching, and agent/organization publishing with hierarchy support.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bopen-tools:clawnet-cliThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
ClawNet CLI uses `@1sat/[email protected]` and `@1sat/wallet-mac` for key management. The old `configureVault()` helper and built-in `se-helper` binary have been removed.
ClawNet CLI uses @1sat/[email protected] and @1sat/wallet-mac for key management. The old configureVault() helper and built-in se-helper binary have been removed.
The vault is composed from three pieces:
SecureEnclaveProvider from @1sat/wallet-mac — platform-specific Secure Enclave operations. Instantiated with SecureEnclaveProvider({ name: "ClawNet" }).FileVaultStorage from @1sat/vault — file-based vault entry storage.createVault(provider, storage) from @1sat/vault — creates the vault instance from a provider and storage backend.import { SecureEnclaveProvider } from "@1sat/wallet-mac";
import { FileVaultStorage, createVault } from "@1sat/vault";
const provider = new SecureEnclaveProvider({ name: "ClawNet" });
const storage = new FileVaultStorage();
const vault = createVault(provider, storage);
clawnet add fetches files via /content/{manifest}/{path} directory paths. ORDFS resolves _N refs and nested directories natively, so the CLI no longer needs to parse them manually. The old downloadDirectoryEntries function with manual _N parsing was removed.
Example fetch path:
https://ordfs.network/content/{manifestTxid}/src/index.ts
ORDFS handles the directory tree resolution server-side.
clawnet publish ORGANIZATION.md publishes organization packages with an agent hierarchy (roles, reporting structure).
The ORGANIZATION.md format uses YAML frontmatter with an agents: array:
---
name: my-org
agents:
- slug: lead-agent
role: lead
- slug: worker-agent
role: worker
reportsTo: lead-agent
---
Each agent entry supports:
slug — agent identifier (must match a published agent)role — the agent's role within the organizationreportsTo — slug of the agent this one reports to (establishes hierarchy)Agent .md files support an icon: field in YAML frontmatter. The icon URL points to an avatar image that is stored in the registry and served via the API.
---
name: my-agent
icon: https://example.com/avatar.png
---
npx claudepluginhub b-open-io/claude-plugins --plugin bopen-toolsImports an OpenClaw agent workspace (SOUL.md, IDENTITY.md, MEMORY.md, etc.) into the current project. Useful when migrating or referencing an agent's identity and memory.
Exposes the DashClaw platform's routes, schema, and env vars via snapshot and live queries. Use for integration, troubleshooting, and governance — prefers `python -m livingcode query` or REST fallback.
Runs a checklist for onboarding new agents to the bOpen team: design, write, avatar, plugin, Paperclip registration, roster, and optional ClawNet bot deployment.