Implemented optional authentication to keep strangers out of the
Claude OS frontend when deployed to production servers.
Backend (FastAPI):
- mcp_server/auth.py: JWT-based authentication
* Bcrypt password hashing
* Environment-based user credentials (no database needed)
* 7-day token expiration
* Optional - disabled by default
- mcp_server/server.py: Auth endpoints
* POST /api/auth/login - Returns JWT token
* GET /api/auth/me - Get current user
* GET /api/auth/status - Check if auth enabled
- requirements.txt: Added dependencies
* passlib[bcrypt] for password hashing
* python-jose[cryptography] for JWT
* python-multipart for form data
Frontend (React):
- frontend/src/lib/auth.tsx: Auth context and hooks
* Manages authentication state
* Automatic token validation
* localStorage for token persistence
- frontend/src/pages/Login.tsx: Beautiful login page
* Gradient design matching Claude OS branding
* Clear error messages
* Loading states
- frontend/src/components/ProtectedRoute.tsx: Route protection
* Automatically redirects to login if not authenticated
* Shows loading state during auth check
* Bypasses auth if disabled
- frontend/src/App.tsx: Integrated auth
* Wrapped app in AuthProvider
* Protected routes for Welcome and MainApp
* Login route for authentication
Documentation:
- AUTH_SETUP.md: Complete authentication guide
* Quick start instructions
* Password hash generation
* Production deployment steps
* Troubleshooting guide
- .env.example: Added auth configuration
* CLAUDE_OS_EMAIL (login email)
* CLAUDE_OS_PASSWORD (dev - plain text)
* CLAUDE_OS_PASSWORD_HASH (production - bcrypt hash)
* CLAUDE_OS_SECRET_KEY (JWT secret)
- docs/PRODUCTION_DEPLOYMENT.md: Added Step 5
* Authentication setup for production
* Hash and secret generation commands
* Testing instructions
Features:
✅ Optional authentication (disabled by default)
✅ Single user via environment variables
✅ Secure bcrypt hashing
✅ JWT tokens with 7-day expiration
✅ Beautiful login UI
✅ No database required for user management
Usage:
1. Set CLAUDE_OS_EMAIL and CLAUDE_OS_PASSWORD in .env
2. Restart Claude OS
3. Visit /login to authenticate
4. Token valid for 7 days
To disable auth: Remove CLAUDE_OS_EMAIL from .env
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Documented the brilliant discovery: copy local SQLite database
to production server to transfer ALL accumulated knowledge instantly!
Why this is game-changing:
- All of Claude's memories about bugs, solutions, patterns
- All indexed code and documentation
- Every architectural decision made locally
- Months of accumulated knowledge → instant production
- No re-indexing needed (saves hours!)
Updated:
- docs/PRODUCTION_DEPLOYMENT.md:
* Added Step 3: Copy Local SQLite Database to Server
* Complete instructions with verification steps
* Explains benefits of knowledge transfer
* Fixed step numbering (4, 5, 6)
- docs/QUICK_REFERENCE.md:
* Added "Copy Local Database to Production" section
* Quick reference for database transfer
* Labeled as "SECRET SAUCE!" for emphasis
Deployment flow:
1. Deploy Claude OS to server
2. Copy local database with scp
3. Replace server database
4. Restart services
5. Production Claude now has ALL local knowledge!
This transforms deployment from "start from scratch" to
"transfer institutional knowledge instantly"
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Created comprehensive indexing script to index entire codebases
into Claude OS knowledge bases with a single command.
New Files:
- scripts/index-codebase.sh: Automated codebase indexing script
* Intelligently detects project structure (Rails, Node.js, etc.)
* Indexes docs, source code, models, services, controllers, config
* Provides progress indicators and statistics
* Handles errors gracefully
* Can be run locally or on production servers
- scripts/README.md: Complete documentation for helper scripts
* Usage examples for local and production
* Integration with Capistrano, Docker, GitHub Actions
* Cron job setup for automatic re-indexing
* Troubleshooting guide
Updated:
- docs/PRODUCTION_DEPLOYMENT.md:
* Added section on keeping code index updated
* Capistrano hook example for auto-indexing on deploy
* Cron job setup for scheduled re-indexing
* Performance impact notes
Benefits:
- One command indexes entire codebase across all knowledge bases
- Complete context for Claude (semantic search across all code)
- Pattern recognition from your coding style
- Better code suggestions matching your architecture
- Re-index on every deployment to stay current
Usage:
./scripts/index-codebase.sh Pistn /path/to/project http://localhost:8051🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
