Implement zero-friction authentication persistence with MCP user scope
Major breakthrough solving the authentication chicken-and-egg problem: Key Changes: - Copy ~/.claude.json and ~/.claude/ during Docker build for baked-in auth - Add -s user flag to claude mcp add-json for persistent MCP servers - Simplify rebuild logic to prevent unnecessary rebuilds - Update documentation with rebuild instructions Technical Details: - Authentication files placed before USER switch in Dockerfile - MCP configuration now persists across all sessions - Rebuild only occurs when image doesn't exist - Clean separation of build vs runtime concerns Result: Users authenticate once on host, then zero login prompts forever. SMS notifications ready immediately on container start.
This commit is contained in:
5
.gitignore
vendored
5
.gitignore
vendored
@@ -26,5 +26,10 @@ data/
|
||||
*.tmp
|
||||
*.temp
|
||||
~*
|
||||
|
||||
# Claude authentication files (copied during build)
|
||||
.claude.json
|
||||
.claude/
|
||||
|
||||
# Environment file with credentials
|
||||
.env
|
||||
|
Reference in New Issue
Block a user