Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Delve

github.com

  • Free plan
  • Windows
  • macOS
  • Linux
  • API
  • Self-hosted
7.6 Club score Visit github.com

What Delve is

Delve is a free, MIT-licensed debugger for Go, designed for command-line use and separate clients. It can debug, execute, and test programs, including headless operation. Developers can control execution, evaluate variables, and inspect threads, goroutines, and CPU registers. Commands cover attaching to processes, debugging or testing packages, running precompiled binaries, tracing, examining core dumps, and replaying rr traces. Headless Delve exposes a JSON-RPC 1.0 API in APIv1 and APIv2, with controls such as halt, continue, next, step, and stepout. Integrations are listed for GoLand, IntelliJ IDEA, Vim, Neovim, Visual Studio Code, Emacs, and other editors. Pre-built binaries target Linux, macOS, and Windows, while installation through Go is documented. The FAQ lists Linux amd64, arm64, and 386; Windows amd64; and macOS amd64 as supported combinations. Remote debugging is supported, but headless connections are unauthenticated and can permit arbitrary remote code execution.

Who it suits

Delve suits Go developers who need command-line debugging, editor integration, API control, or remote sessions. It fits teams working on the listed Linux, Windows, macOS, or documented FreeBSD environments.

Good to know, and what to watch

  • Free MIT-licensed Go debugger
  • Supports debugging, testing, tracing, and core dumps
  • Offers JSON-RPC headless APIs
  • Integrates with major Go editors
  • Provides conditional, exception, and time-travel debugging
  • Headless connections are unauthenticated and unsafe for production
  • Supported architectures are limited by the FAQ
  • Go installation requires version 1.16 or later
  • Remote access should use SSH tunnels or a VPN

The verdict

Delve covers detailed Go execution control through command-line, editor, and API interfaces. Its documented architecture limits and serious headless-connection security warning require careful deployment planning.

What the maker publishes

Alternative interfaces
The project lists Gdlv and Debugger as alternative user interfaces for Delve. source
Architecture limits
The FAQ says other operating systems and architectures are unsupported and have no planned support ETA. source
Client API
A headless Delve instance exposes an API built on JSON-RPC 1.0, with APIv1 and APIv2 versions. source
Debug commands
Its documented commands include attaching to a running process, debugging or testing a package, executing a precompiled binary, tracing a program, examining a core dump, and replaying an rr trace. source
Debugger controls
Its API supports commands including halt, continue, next, step, and stepout. source
Debugging
It lets users control program execution, evaluate variables, and inspect thread, goroutine, and CPU register state. source
Debugging modes
The command line supports debugging, executing, and testing programs, including headless mode for a separate client. source
Downloads
Pre-built binaries are available for Linux, macOS, and Windows, and the project also documents installation with Go. source
Editor integrations
The project lists integrations for GoLand, IntelliJ IDEA, Vim and Neovim, Visual Studio Code, Emacs, and other editors. source
Installation requirement
The documented Go installation command requires Go version 1.16 or later. source
License
The repository identifies its license as MIT. source
License
The repository identifies its license as MIT. source
Operating systems
The installation guide says its instructions are known to work on Linux, macOS, Windows, and FreeBSD. source
Purpose
Delve is a debugger for the Go programming language, designed to be simple to invoke and use. source
Release verification
Installation documentation describes verifying release checksums with cosign and sha256sum. source
Remote debugging
Delve supports remote debugging and recommends SSH tunnels or a VPN when connecting remotely. source
Remote debugging guidance
For remote debugging, the FAQ recommends avoiding public networks and using SSH tunnels or a VPN if remote access is necessary. source
Remote debugging security
The FAQ warns that headless remote connections are unauthenticated and can allow arbitrary remote code execution, and says not to use this setup in production. source
Security
The FAQ warns that headless connections are unauthenticated and allow arbitrary remote code execution, and says not to use them in production. source
Support
The project says its GitHub issue tracker is for bug reports and directs feature proposals and discussions to the developer mailing list. source
Support channel
The README says the issue tracker is for bugs and directs feature proposals and discussions to the developer mailing list. source
Supported systems
The FAQ lists Linux on amd64, arm64, and 386, Windows on amd64, and macOS on amd64 as supported combinations. source
Supported targets
The FAQ lists Linux amd64, arm64, and 386; Windows amd64; and macOS amd64, and says there is no planned ETA for other operating systems or architectures. source

Checked against the maker's pages on 30 Sept 2026.