Where Does Kilo Code Store Config and Tasks?
Kilo Code reads shared kilo.jsonc configs globally and per project, with task history in VS Code global storage.
Last updated
Kilo Code centers on JSONC files, not VS Code settings. Global defaults live in a kilo folder under your config home. Project overrides sit as kilo.jsonc or .kilo kilo.jsonc in the repo root. CLI, VS Code, and JetBrains clients all read the same pair.
Task transcripts and MCP settings from the legacy extension era sit in VS Code globalStorage under kilocode.kilo-code. Export from Settings gear menu writes kilo-code-settings.json (usually to Documents) for sharing. Reset there wipes keys, modes, and history permanently.
Where Kilo Code stores this, by platform
C:\Users\[Username]\.config\kilo\kilo.jsonc
Legacy extension tasks in %APPDATA%\Code\User\globalStorage\kilocode.kilo-code. CLI runtime state in %USERPROFILE%\.kilocode\cli. Override base with kilo-code.customStoragePath.
~/.config/kilo/kilo.jsonc
Legacy tasks in ~/Library/Application Support/Code/User/globalStorage/kilocode.kilo-code. Project file kilo.jsonc or .kilo/kilo.jsonc beside code. Migrating from opencode means moving config out of .opencode dirs.
~/.config/kilo/kilo.jsonc
Legacy tasks in ~/.config/Code/User/globalStorage/kilocode.kilo-code. JetBrains wrapper adds ~/.kilocode globalStorage and workspaceStorage plus secrets.json.
Frequently asked questions
How do I back up Kilo Code settings?
Copy the global kilo.jsonc plus any project kilo.jsonc files. Use Settings Export for a shareable kilo-code-settings.json snapshot including provider profiles.
Where did my old Kilo Code task history go?
Legacy history sits under the kilocode.kilo-code globalStorage tasks tree per VS Code variant (Code versus Insiders versus Cursor). Point a file browser there and copy task folders before resetting.
Notice an outdated path? Let us know.