Skip to content
NerveDocs

Get started with Nerve

Nerve is a local-first desktop coding harness for people who want an agent’s work to stay visible and controllable. This path takes you from installation to a small, reviewed change with supervised permission.

Your first run

Section titled “Your first run”
  1. Install Nerve. Launch the desktop app from npm or a source checkout. You need Node.js 24 or newer.
  2. Connect a model provider. Choose API-key or OAuth authentication, then select a default model.
  3. Open a project. Select a local directory and begin with Coding mode plus Supervised permission.
  4. Complete a safe first task. Inspect first, review approvals and diffs, run focused validation, and verify the final Git state yourself.
Nerve workbenchThe Nerve desktop workbench showing a completed Bash result, two sub-agent assignment cards, and the expanded Agents activity island above the composerThe Nerve desktop workbench showing a completed Bash result, two sub-agent assignment cards, and the expanded Agents activity island above the composer
What to notice: What to notice: command results and sub-agent assignments share the transcript. The expanded Agents activity island keeps delegated work accessible above the composer.

Choose the path you need

Section titled “Choose the path you need”
Learn the daily workflowNavigate conversations, the composer, reviews, files, Git, pull requests, launch configurations, and background commands.
Configure models and integrationsConnect providers, select models, and enable optional Web, Python, Atlassian, or browser guidance.
Operate Nerve safelyUnderstand configuration, storage, security, browser access, LAN/mobile use, and remote daemons.
Build and extend NerveExplore package boundaries, the harness, tools, persistence, and Protocol v1.

Understand the product first

Section titled “Understand the product first”

If you are still evaluating Nerve, start with What is Nerve? for the local-first topology, core concepts, and authority model. For a symptom you are already troubleshooting, use the troubleshooting index.