This development container provides a standardized environment for developing Kilo Code.
Kilo Code stores thread conversations, settings, and caches in the following locations:
~/.vscode-remote/data/User/globalStorage/kilocode.kilo-code/~/.vscode-remote/data/User/settings/~/.vscode-remote/data/User/globalStorage/kilocode.kilo-code/cache/~/.vscode-remote/data/User/globalStorage/kilocode.kilo-code/vector/The dev container is configured with named volumes to persist this data across container rebuilds:
| Volume | Target | Purpose |
|---|---|---|
kilocode-global-storage |
/root/.vscode-remote/data/User/globalStorage/kilocode.kilo-code |
Threads, cache, vector store |
kilocode-settings |
/root/.vscode-remote/data/User/settings |
VS Code settings |
When you rebuild the dev container, these volumes persist your data:
If threads don't appear after a container rebuild:
Verify volumes exist:
docker volume ls | grep kilocode
Inspect volume contents:
docker volume inspect kilocode-global-storage
Reattach volumes: If volumes were detached, rebuild with:
devcontainer rebuild
Manual recovery: If volumes are lost, threads cannot be recovered. Start new conversations and consider backing up important threads.
To back up your threads:
Copy the global storage directory:
cp -r ~/.vscode-remote/data/User/globalStorage/kilocode.kilo-code ~/kilocode-backup
Store the backup outside the dev container environment.
If you need threads stored in a different location, configure a custom storage path in VS Code settings:
Ctrl+, or Cmd+,)Example devcontainer.json mount for custom path:
"mounts": [
{
"source": "/path/on/host/kilocode-data",
"target": "/home/vscode/kilocode-data",
"type": "bind"
}
]
Then set the custom storage path to /home/vscode/kilocode-data.