This reference is joined directly from the generated adapter registry metadata and the ID-keyed setup overlay. It stays in registry order and exposes each target’s generation and application capabilities, environment, sample filename, source implementation, and paths.
The generated file is a gui.theme snippet; Lazygit does not automatically read Theme Manager’s applied path.
material_dark_lazygit_theme.yml~/.config/lazygit/themes/{theme}_{mode}_lazygit_theme.yml~/.config/lazygit/theme.ymlInclude the stable gitconfig fragment once.
material_dark.gitconfig~/.config/delta/themes/{theme}_{mode}.gitconfig~/.config/delta/theme.gitconfigTheme Manager copies the palette and maintains Zellij’s three theme selection keys.
material_dark.kdl~/.config/zellij/themes/{theme}_{mode}.kdl~/.config/zellij/theme.kdl and config.kdlGenerated plugin styling is installed as Zellij’s default layout.
material_dark.kdl~/.config/zellij/layouts/material_generated/{theme}_{mode}.kdl~/.config/zellij/layouts/default.kdlTermux reads its fixed colors.properties path directly.
material_dark.properties~/.termux/colors/{theme}_{mode}.properties~/.termux/colors.propertiesPoint Ghostty at the permanent theme name, not at an individual generated theme.
material_dark~/.config/ghostty/themes/{theme}_{mode}~/.config/ghostty/themeImport Theme Manager’s stable theme file once; every later selection replaces that file.
material_dark.toml~/.config/alacritty/material_themes/{theme}_{mode}.toml~/.config/alacritty/theme.tomlTheme Manager stages a stable TOML file, but Rio theme inclusion depends on the Rio version you run.
material_dark.toml~/.config/rio/themes/{theme}_{mode}.toml~/.config/rio/theme.tomlLoad the generated Lua pointer once; Theme Manager updates its color_scheme value on selection.
material_dark.toml~/.config/wezterm/themes/{theme}_{mode}.toml~/.config/wezterm/theme.toml and config/theme.luaKitty already reads its light and dark auto-theme files.
material_dark.conf~/.config/kitty/material_themes/{theme}_{mode}.conf~/.config/kitty/light-theme.auto.conf and dark-theme.auto.confThe generated YAML is a color reference, not a file Eza consumes directly.
material_dark.yml~/.config/eza/themes/{theme}_{mode}.yml~/.config/eza/theme.ymlSource the stable shell fragment after your base FZF options.
material_dark.sh~/.config/fzf/material_themes/{theme}_{mode}.sh~/.config/fzf/theme.shPin one stable theme name; Atuin re-reads that file every time the history search opens.
material_dark.toml~/.config/atuin/themes/generated/{theme}_{mode}.toml~/.config/atuin/themes/tman.tomlYazi reads its fixed theme.toml path directly.
material_dark.toml~/.config/yazi/material_themes/{theme}_{mode}.toml~/.config/yazi/theme.tomlOn rooted Android devices, Theme Manager installs the selected XML directly into MiXplorer’s private storage.
material_dark.xml~/.config/mixplorer/themes/{theme}_{mode}.xml/data/data/com.mixplorer.silver/files/theme/properties.xmlTheme Manager discovers supported installed IDEs and installs a theme plugin JAR into each one.
material.jar~/.config/jetbrains/themes/{theme}.jarEach IDE’s plugins/themes/material-theme.jarLoad Theme Manager’s per-mode pointer from your Neovim configuration.
material_dark.lua~/.config/nvim/colors/{theme}_{mode}.lua~/.config/nvim/lua/settings/current.luaVS Code receives a packaged extension; tman select does not install or switch it.
material.vsix~/.vscode/extensions/material-themes-generated/{theme}.vsixNo select-time destinationPin OpenCode to Theme Manager’s permanent proxy theme name.
material_dark.json~/.config/opencode/themes/generated/{theme}_{mode}.json~/.config/opencode/themes/tman.jsonCreate the proxy before OMP starts, then pin both automatic appearance slots to it.
material_dark.json${PI_CODING_AGENT_DIR:-$HOME/.omp/agent}/themes/generated/{theme}_{mode}.json${PI_CODING_AGENT_DIR:-$HOME/.omp/agent}/themes/tman.jsonCreate the bridge theme before pinning it, then point Pi's settings at that one name.
material_dark.json${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}/themes/generated/{theme}_{mode}.json${PI_CODING_AGENT_DIR:-$HOME/.pi/agent}/themes/tman.jsonFor setup steps, response details, and caveats, see the full integrations catalogue.