id       = "warp"
name     = "Warp"
homepage = "https://www.warp.dev"
description = "The agentic development environment."
icon     = "SimpleIcons:warp"
executables   = ["warp"]

[dotfiles]

# https://docs.warp.dev/terminal/settings/file-locations is Warp's own table of
# where everything goes, and it is three genuinely different layouts rather
# than one location under three names, so each is written out. Warp's own
# headings split the list: "portable user data" (themes, tab configs, workflows,
# launch configurations) and "non-portable config" (settings.toml,
# keybindings.yaml) — both are the user's own settings; the third heading,
# "non-portable state", covers the logs, the database and the Codebase Context
# index and none of it is listed here.
#
#   macOS   ~/.warp/… , a literal dotfile directory
#   Linux   ${XDG_DATA_HOME:-$HOME/.local/share}/warp-terminal/… for the
#           portable data and ${XDG_CONFIG_HOME:-$HOME/.config}/warp-terminal/…
#           for the config — Warp reads both variables, so those are [xdgData]
#           and [configHome] rather than literal paths
#   Windows %APPDATA%\warp\Warp\data\… for the portable data and
#           %LOCALAPPDATA%\warp\Warp\config\… for the config, which is why
#           neither Windows half can be folded into a placeholder with its
#           Unix counterpart
#
# The MCP server config is the one file the page marks "cross-platform":
# ~/.warp/.mcp.json on all three, spelled %USERPROFILE%\.warp\.mcp.json on
# Windows, which is the same path.
paths = [
  "~/.warp/themes/",
  "~/.warp/tab_configs/",
  "~/.warp/default_tab_configs/",
  "~/.warp/workflows/",
  "~/.warp/launch_configurations/",
  "~/.warp/settings.toml",
  "~/.warp/keybindings.yaml",
  "~/.warp/.mcp.json",
  "[xdgData]/warp-terminal/themes/",
  "[xdgData]/warp-terminal/tab_configs/",
  "[xdgData]/warp-terminal/default_tab_configs/",
  "[xdgData]/warp-terminal/workflows/",
  "[xdgData]/warp-terminal/launch_configurations/",
  "[configHome]/warp-terminal/settings.toml",
  "[configHome]/warp-terminal/keybindings.yaml",
  "%APPDATA%/warp/Warp/data/themes/",
  "%APPDATA%/warp/Warp/data/tab_configs/",
  "%APPDATA%/warp/Warp/data/default_tab_configs/",
  "%APPDATA%/warp/Warp/data/workflows/",
  "%APPDATA%/warp/Warp/data/launch_configurations/",
  "%LOCALAPPDATA%/warp/Warp/config/settings.toml",
  "%LOCALAPPDATA%/warp/Warp/config/keybindings.yaml",
]

# Everything the page files under "non-portable state" is outside the
# directories above — ~/Library/Logs/warp.log*, the Group Containers database
# on macOS, %LOCALAPPDATA%\warp\Warp\data\ on Windows,
# ${XDG_STATE_HOME:-$HOME/.local/state}/warp-terminal/ on Linux — so there is
# nothing to carve out of what is listed. ~/.warp/skills/ is left out for a
# different reason: the page calls it "bundled skills", which Warp ships rather
# than the user writing.

# No credential file under the home directory. The signed-in account lives in
# the database the page files under non-portable state, not in a file beside
# the settings.
secret = []

# No secret_paths for .mcp.json. An MCP server definition is the usual place a
# pasted API token ends up, but Warp's docs name the file without publishing
# its key names, and a key_path written from a guess would resolve to nothing
# and quietly protect nothing. A consumer that scans content still catches it.
#
# No machine_lines either: settings.toml and keybindings.yaml are appearance,
# shell and key-binding preferences, which is what a user wants carried.