# Nerve **The cockpit OpenClaw deserves.** *OpenClaw is powerful. Nerve is the interface that makes people say “oh, now I get it."* [![Star Nerve on GitHub](https://img.shields.io/github/stars/daggerhashimoto/openclaw-nerve?style=for-the-badge&logo=github&label=Star%20Nerve%20on%20GitHub&color=0f172a)](https://github.com/daggerhashimoto/openclaw-nerve) [![MIT License](https://img.shields.io/badge/license-MIT-blue?style=for-the-badge)](LICENSE) [![Discord](https://img.shields.io/discord/1474924531683688478?style=for-the-badge&color=5865F2&logo=discord&logoColor=white&label=Discord)](https://discord.gg/Sh9ZGtctva)

```bash curl -fsSL https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/install.sh | bash ``` > *Run the installer, live in 60 seconds*

Mobile Screenshots

## Why Nerve exists Chat is great for talking to agents. It is not enough for operating them. The moment you care about visibility, control and coordination over your agents, the thread gets too small. You want the workspace, sessions, taskboard, editor, usage, and agent context in one place. *Nerve is that place.* ## Why it feels different ### ✨ Fleet control, not just chat Run multiple agents from one place. Each agent can have its own workspace, subagents, memory, identity, soul, and skills, while Nerve gives you a single control plane to switch context, inspect state, and operate the whole fleet. ### ✨ Voice that feels built in Push-to-talk, wake word flows, explicit language selection, local Whisper transcription, multilingual stop and cancel phrases, and multiple TTS providers. Voice is part of the product, not an afterthought. ### ✨ Full agent operating context Each agent can have its own workspace, memory, identity, soul, and skills. Nerve lets you inspect, edit, and manage that context live, without guessing what an agent knows, where it works, or how it is configured. ### ✨ A real operating layer Crons, session trees, kanban workflows, review loops, proposal inboxes, and model overrides. Nerve gives agent work an operating surface instead of leaving it trapped inside chat history. ### ✨ Rich live output Charts, diffs, previews, syntax-highlighted code, structured tool rendering, and streaming UI that makes agent responses easier to inspect. >

> >

What you can do with it

> > - **Talk to your agent by voice** and hear it answer back naturally > - **Browse and edit the workspace live** while the conversation is still happening > - **Watch cron runs as separate sessions** instead of treating automation like a black box > - **Delegate work onto a kanban board** and review what came back > - **Ask for a chart** and get a real chart, not a code block pretending to be one > - **Track token usage, costs, and context pressure** while long tasks run > - **Inspect subagent activity** without losing the main thread > - **Switch between per-agent workspaces and memory** without losing context > - **Inspect each agent’s identity, soul, and skills** from the UI > - **Delegate subagent work inside a larger agent fleet** instead of treating everything as one thread

## Capability snapshot | Area | Highlights | |---|---| | **Agent fleet** | Run multiple agents from one control plane, each with its own workspace, subagents, memory, identity, soul, and skills | | **Interaction** | Streaming chat, markdown, syntax highlighting, diff views, image paste, file previews, voice input, TTS, live transcription preview | | **Workspace** | Per-agent file browser, tabbed editor, memory editing, config editing, skills browser | | **Operations** | Session tree, subagents, cron scheduling, kanban task board, review flow, proposal inbox, model overrides | | **Observability** | Token usage, cost tracking, context meter, agent logs, event logs | | **Polish** | Command palette, responsive UI, 14 themes, font family and 10px to 24px font size controls, mobile-safe input sizing, hot-reloadable settings, updater with rollback | ## Get started ### One command ```bash curl -fsSL https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/install.sh | bash ``` > *The installer handles dependencies, clone, build, and then usually hands off straight into the setup wizard. Guided access modes include localhost, LAN, Tailscale tailnet IP, and Tailscale Serve.* ### Pick your setup - **[Local](docs/DEPLOYMENT-A.md)** — Run Nerve and Gateway on one machine. *Recommended default setup for reliability and simplicity.* - **[Hybrid](docs/DEPLOYMENT-B.md)** — Keep Nerve local, run Gateway in the cloud - **[Cloud](docs/DEPLOYMENT-C.md)** — Run Nerve and Gateway in the cloud

Try the next branch

`master` is the stable branch. Use `next` if you want the latest Nerve work before it lands in `master`. Fresh install from `next`: ```bash curl -fsSL https://raw.githubusercontent.com/daggerhashimoto/openclaw-nerve/master/install.sh | bash -s -- --branch next ``` Switch an existing install to `next`: ```bash cd ~/nerve # installer default; manual clone: cd openclaw-nerve git fetch origin git switch next || git switch -c next --track origin/next git pull --ff-only npm install npm run build npm run prod ``` Keep `next` updated: ```bash cd ~/nerve # installer default; manual clone: cd openclaw-nerve git fetch origin git switch next || git switch -c next --track origin/next git pull --ff-only npm install npm run build npm run prod ``` `next` can change quickly. Use it if you are comfortable testing early builds.

Manual install

```bash git clone https://github.com/daggerhashimoto/openclaw-nerve.git cd openclaw-nerve npm install npm run setup npm run prod ```

Updating

```bash npm run update -- --yes ``` Fetches the latest release, rebuilds, restarts, verifies health, and rolls back automatically on failure.

Development

```bash npm run dev # frontend — Vite on :3080 by default PORT=3081 npm run dev:server # backend — explicit split-port dev setup ``` `npm run dev:server` uses the normal server `PORT` setting. If you do not override it, the backend also defaults to `:3080` and will collide with Vite. **Requires:** Node.js 22+ and an OpenClaw gateway.

## How it fits into OpenClaw Nerve sits in front of the gateway and gives you a richer operating surface in the browser. ```text Browser ─── Nerve (:3080) ─── OpenClaw Gateway (:18789) │ │ ├─ WS ──────┤ proxied to gateway ├─ SSE ─────┤ file watchers, real-time sync └─ REST ────┘ files, memories, TTS, models ``` OpenClaw remains the engine. Nerve gives it a cockpit. **Frontend:** React 19 · Tailwind CSS 4 · shadcn/ui · Vite 7 **Backend:** Hono 4 on Node.js ## Security Nerve binds to `127.0.0.1` by default, so it stays local unless you choose to expose it. When you bind it to the network (`HOST=0.0.0.0`), built-in password authentication protects the UI and its endpoints. Sessions use signed cookies, passwords are stored as hashes, WebSocket upgrades are authenticated, and trusted connections can use server-side gateway token injection. For the full threat model and hardening details, see **[docs/SECURITY.md](docs/SECURITY.md)**. ## Documentation - **[Architecture](docs/ARCHITECTURE.md)** — codebase structure and system design - **[Configuration](docs/CONFIGURATION.md)** — `.env` variables and setup behavior - **[Deployment Guides](docs/README.md)** — local, hybrid, and cloud setups - **[Agent Markers](docs/AGENT-MARKERS.md)** — TTS, charts, kanban markers, and rich UI output - **[Troubleshooting](docs/TROUBLESHOOTING.md)** — common issues and fixes - **[Tailscale Guide](docs/TAILSCALE.md)** — private remote access via tailnet IP or Tailscale Serve - **[Contributing](CONTRIBUTING.md)** — development workflow and pull requests - **[Changelog](CHANGELOG.md)** — release notes and shipped changes ## Community If this is the kind of interface you want around your OpenClaw setup, give the repo a star, contribute and keep an eye on it. Join the **[Nerve Discord](https://discord.gg/Sh9ZGtctva)** to get help, discuss, share your setup, and follow development. ### People building Nerve [![Contributors](https://contrib.rocks/image?repo=daggerhashimoto/openclaw-nerve)](https://github.com/daggerhashimoto/openclaw-nerve/graphs/contributors) ## License [MIT](LICENSE)