Repository navigation
feat: seed CLAUDE.md on first start to give remote sessions workspace context - #3
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
/workspace/CLAUDE.mdat container startup if one does not already existBackground
In
--remote-controlmode, conversation history is managed by the relay and is not preserved across pod restarts. Session files on disk are cache/metadata only; there is no--resumeflag. Without any workspace context file, Claude starts each new session with zero awareness of where it's running or what tools/paths are available.A seeded CLAUDE.md is the standard Claude Code pattern for this — lightweight and overridable.
Test plan
sh -n entrypoint.shpassesdocker buildsucceedsCLAUDE.mdis present at/workspace/CLAUDE.md/workspace/CLAUDE.md: file is NOT overwritten🤖 Generated with Claude Code