Where Does Delve Store Configs?
Where Delve keeps configs on computers, for Go debugging state and files. Exact folders are covered below.
Last updated
Delve is Go debugging with file configs. Your aliases and themes live in its config directory at home. Sessions hold breakpoints only while running.
Same config means same setup on any machine with Go installed. Exact file names are stable across late releases. Keep configs in dotfiles repos rather than cloning whole folders. For moves, copy the directory. Partial copies miss substitute path rules that sessions depend on. When in doubt, verify paths inside the app before trusting a remembered folder.
Where Delve Debugger stores this, by platform
%userprofile%\.dlv (aliases, themes beside it)
Aliases live in the Delve config directory at home. Copy it for moves. Match Go releases for DWARF handling. Keep files in dotfiles repos.
~/.config/dlv (aliases, themes beside it)
Same config model on Linux under the home directory. Sessions hold breakpoints while running only. Script repeating setups in config files.
Frequently asked questions
How do I move Delve configs to a new computer?
Copy the Delve config directory to the new machine over USB, since breakpoints live per session unless scripted. Config files hold aliases and themes. Match the Go release first, since DWARF handling shifts between versions.
Does Delve sync online?
No. Delve runs Go debugging from its config directory without a central database. The home folder holds aliases plus theme files. Targets load per session only. Back up the config directory itself for moves.
Notice an outdated path? Let us know.