Delve is a debugger for the Go programming language.
24.8k
Stars
2.2k
Forks
83
Open issues
30
Contributors
AI Analysis
Delve is a debugger for the Go programming language, providing a full-featured debugging tool designed to be simple and non-intrusive. It serves Go developers who need interactive debugging capabilities for development and troubleshooting. This is a specialized tool for the Go ecosystem—not relevant to developers working in other languages.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Delve: The de facto debugger for Go, actively maintained after 12 years
Delve is a purpose-built debugger for the Go programming language, offering full-featured debugging capabilities including breakpoints, stack inspection, goroutine introspection, and remote debugging. It is the standard debugger used by Go developers across the ecosystem, integrated into every major Go-capable IDE and editor (VS Code via vscode-go, GoLand, Vim via vim-go, Emacs, etc.). It matters because Go's runtime model — goroutines, garbage collection, unique calling conventions — required a debugger built specifically for the language rather than a generic GDB adaptation.
Founded in May 2014 by Derek Parker as the Go ecosystem was maturing. It emerged because GDB support for Go was inadequate. Over time it became the official debugger recommended by the Go team and is now maintained by a core group of contributors.
Growth tracked closely with Go's own adoption curve from 2014–2020. Stars and adoption plateaued at a high baseline as Delve became the undisputed standard — not because interest declined, but because the market saturated. New Go developers automatically adopt Delve via editor integrations without ever starring the repo. Recent 7-day star gain of 7 reflects a mature, settled tool rather than a declining one.
Delve is bundled or auto-installed by the official vscode-go extension (tens of millions of VS Code Go users), JetBrains GoLand, and vim-go. It is referenced in official Go documentation. Its integration depth across the entire Go tooling ecosystem constitutes strong indirect evidence of widespread production usage, even without explicit download telemetry published in the README.
Likely implements a custom debug backend that interfaces with Go's runtime and DWARF debug info, exposing a DAP (Debug Adapter Protocol) server and a JSON-RPC API. Appears to support headless mode for IDE integration and a native CLI client. The separation of client/server and documented API surface suggests a layered architecture designed for extensibility.
Not documented in README, but the presence of a dedicated TeamCity CI build aggregator and active contribution guidelines suggests systematic automated testing. Exact coverage metrics are not publicly stated in the README.
Extremely strong. Last push was June 23, 2026 — one day before the evaluation date. The project has been continuously active for 12 years with no visible gaps. Dedicated CI infrastructure (TeamCity), a formal mailing list, structured contribution docs, and an explicit AI usage policy all indicate an organized, professionally maintained project.
ADOPT IF: you are writing Go code and need interactive debugging — Delve is the standard tool with no serious alternatives. AVOID IF: you need time-travel debugging or are debugging non-Go code; Delve is Go-specific by design. MONITOR IF: you are tracking whether the project keeps pace with new Go runtime versions (e.g., new GC, generics edge cases) as language evolution is the primary long-term risk.
Independent dimensions
Mainstream potential
5/10
Technical importance
9/10
Adoption evidence
8/10
- Go runtime changes (new GC, register-based calling conventions, generics) can temporarily break or lag Delve's accuracy until maintainers catch up — this has happened historically with major Go releases.
- Maintainer concentration risk: the project appears to depend on a relatively small core team; loss of key contributors could slow response to Go version changes.
- Windows and macOS debugging support has historically lagged behind Linux; platform parity may remain an ongoing concern for cross-platform teams.
- DAP (Debug Adapter Protocol) spec evolution or IDE-side changes could require continuous adapter maintenance work.
- No commercial backer is publicly identified, meaning long-term sustainability depends entirely on volunteer and community contribution.
Delve will remain the standard Go debugger for the foreseeable future, evolving in lockstep with Go releases. Mainstream potential is capped by Go's own market size, but within that space its dominance appears durable.
Explore similar
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Go
- License
- MIT
- Last updated
- 22h ago
- Created
- 148mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
print var infomation have error
telemetry report: pkg/proc: evalCallInjectionSetTarget missing an argument
Console: Option to expand "\n", "\t" and other formatting characters
dlv test does not pass -test.fuzzcachedir=
proc: telemetry report: index error in fncallPeek while resuming execution of a call injection
Open pull requests
Top contributors
Similar repos
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
go-delve/delve
this
|
24.8k | +17 | Go | 8/10 | 22h ago |
 loov/goda
|
1.7k | — | Go | 7/10 | 1w ago |
 ktock/buildg
|
1.5k | — | Go | 7/10 | 3w ago |
 fatih/vim-go
|
16.2k | — | Vim Script | 8/10 | 2d ago |
 wagoodman/dive
|
54.3k | — | Go | 8/10 | 7mo ago |
 golang/vscode-go
|
4.3k | — | TypeScript | 8/10 | 21h ago |
GDB has limited Go support and does not understand goroutines or Go's calling conventions well. Delve was built specifically to address these gaps. GDB remains an option for some low-level scenarios but is rarely preferred for Go application debugging.
pprof is a profiler, not a debugger — it addresses performance analysis rather than interactive step-debugging. They are complementary, not competing tools.
Many Go developers historically relied on log statements. Delve offers interactive, live inspection without recompilation, though some developers still prefer log-based approaches for simplicity in certain scenarios.
JetBrains GoLand historically supported both GDB and Delve backends; Delve is now the recommended and default backend, effectively replacing GDB within that IDE ecosystem.
rr offers time-travel debugging on Linux. Delve does not natively support time-travel debugging, though it is a more accessible and cross-platform general-purpose solution for Go.
/statusIcon.svg)