OpenClaw

OpenClaw has grown into its own little operating shape, so this page keeps the moving parts in one place instead of scattering them across infrastructure notes.

This section is the behavior layer: orchestrator, specialist agents, household workflows, voice and media handling, the task board, validation discipline, and the line between what is already live and what is still only a good idea.

The deployment notes still live elsewhere. That keeps the story honest and makes the project easier to read without repeating the same setup details in every page.

In This Section

• OpenClaw Architecture, Agents, And Workflows - the current system view: commander, specialist agents, household routing, voice, board tasks, and how the pieces fit.
• OpenClaw Workspace, Skills, And Use Cases - shape the per-agent workspace, choose the right extension surface, and decide which jobs belong in prompts, skills, or scripts.
• OpenClaw Voice Transcription With whisper.cpp - the working voice path for the current binary: tools.media.audio, a CLI bridge, and a local whisper.cpp server instead of dead-end handler experiments.
• OpenClaw Workforce, Delegation, And Review Patterns - translate the older Mission Control workforce ideas into the current commander-era model, including delegation, reflexion, and research fan-out.
• OpenClaw Operations And Troubleshooting - validate the gateway, router, board, heartbeats, memory, CalDAV, voice path, and channels in a fixed order.

What This Section Covers

• current agent architecture and role boundaries
• current workforce and delegation patterns
• household, weather, voice, and other automation patterns
• voice input, media handling, and whisper.cpp integration
• task-board usage and operator-facing workflows
• smoke tests, troubleshooting order, and runtime maintenance
• draft versus live features, so older notes do not quietly become source of truth again

Related Platform Guides

• OpenClaw On Proxmox - the deployment-side cluster for CT 106, channel wiring, and secure exposure.
• llama.cpp Router Mode On Proxmox - the model-serving layer OpenClaw depends on.
• Cloudflare Tunnel On Proxmox - the external access path for the control UI when it should leave the LAN.

Source Trail

This hub is summarized from the living OpenClaw pages and the deployment guides that feed them:

• OpenClaw Architecture, Agents, And Workflows
• OpenClaw Workspace, Skills, And Use Cases
• OpenClaw On Proxmox

If the main question is how to deploy or expose the surrounding infrastructure, that content still belongs in Proxmox. If the main question is how OpenClaw behaves once it is alive, this section is the right home.