feat(devcontainer): add volume mounts for persistent storage #5746
+210
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Configure devcontainer to persist VS Code settings and Kilo Code state across container rebuilds by adding dedicated volume mounts for: - Global storage (threads, caches, extensions) - User settings Also added workspaceMount and workspaceFolder configuration for better workspace management. Includes documentation for devcontainer persistence setup.
🦋 Changeset detectedLatest commit: 9142477 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6179524650
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This PR adds dev container persistence support for Kilo Code, ensuring that threads, settings, and caches are preserved across container rebuilds. The changes configure named Docker volumes to persist important data that would otherwise be lost when the dev container is rebuilt.
Implementation
The implementation involves three changes:
.devcontainer/devcontainer.json: Added named volume mounts for persisting Kilo Code state:kilocode-global-storage: Persists threads, cache, and vector store data at/root/.vscode-remote/data/User/globalStorage/kilocode.kilo-codekilocode-settings: Persists VS Code settings at/root/.vscode-remote/data/User/settings.devcontainer/README.md: Added comprehensive documentation explaining:apps/kilocode-docs/docs/getting-started/devcontainer-persistence.md: Added user-facing documentation covering:Tradeoffs
Screenshots
N/A
How to Test
Alternatively, check that the named volumes exist:
docker volume ls | grep kilocodeGet in Touch
thomas07374
Fixes #691