Stop chatting with agents. Start operating them.

What it does

Nerve is a browser-based control plane that sits in front of an OpenClaw gateway. It swaps the usual chat thread for a full operating surface: per-agent workspaces, a file editor, session trees, a kanban task board, cost tracking, and built-in voice input with local Whisper transcription and text-to-speech. In short, it turns the agent engine into something you can fly.

The interesting bit

The UI treats agent operations as first-class, not afterthoughts. Cron runs become separate inspectable sessions, subagent activity lives alongside the main thread, and inline charts replace code blocks pretending to be data. Voice is deeply woven in—push-to-talk, wake words, and multilingual stop phrases—rather than bolted on.

Key highlights

• Fleet control: run multiple agents from one plane, each with its own workspace, memory, identity, and skills.
• Built-in voice: local Whisper transcription, multiple TTS providers, push-to-talk, and wake-word flows.
• Live workspace: browse and edit files, memories, and config while conversations are still streaming.
• Operational tooling: kanban board, review loops, proposal inbox, cron scheduling, and session trees.
• Observability: token usage, cost tracking, context pressure meter, and agent event logs.

Caveats

• It is strictly a frontend for OpenClaw; useless without a running gateway.
• The README repeatedly mentions agent “identity,” “soul,” and “skills” without defining what they actually do.

Verdict

Grab this if you are running OpenClaw agents and need visibility beyond a chat thread. Skip it if you are not already committed to that ecosystem; Nerve has nothing to offer on its own.