centaurus-cli 2.0.0

package/AUTH_FLOW.md

@@ -0,0 +1,138 @@
+# Authentication Flow
+
+## Overview
+
+The Centaurus CLI now features an improved authentication flow with a beautiful UI that guides users through the sign-in process.
+
+## First-Time User Experience
+
+When a user starts the CLI for the first time (without an existing session), they will see:
+
+### 1. Welcome Banner
+```
+ ██████╗███████╗███╗   ██╗████████╗ █████╗ ██╗   ██╗██████╗ ██╗   ██╗███████╗
+██╔════╝██╔════╝████╗  ██║╚══██╔══╝██╔══██╗██║   ██║██╔══██╗██║   ██║██╔════╝
+██║     █████╗  ██╔██╗ ██║   ██║   ███████║██║   ██║██████╔╝██║   ██║███████╗
+██║     ██╔══╝  ██║╚██╗██║   ██║   ██╔══██║██║   ██║██╔══██╗██║   ██║╚════██║
+╚██████╗███████╗██║ ╚████║   ██║   ██║  ██║╚██████╔╝██║  ██║╚██████╔╝███████║
+ ╚═════╝╚══════╝╚═╝  ╚═══╝   ╚═╝   ╚═╝  ╚═╝ ╚═════╝ ╚═╝  ╚═╝ ╚═════╝ ╚══════╝
+
+                     ██████╗██╗     ██╗
+                    ██╔════╝██║     ██║
+                    ██║     ██║     ██║
+                    ██║     ██║     ██║
+                    ╚██████╗███████╗██║
+                     ╚═════╝╚══════╝╚═╝
+```
+
+### 2. Authentication Information
+```
+🔐 Authentication Required
+
+To use Centaurus CLI, you need to sign in with Google.
+
+Cloud Sync Features:
+  ✅ Conversation history across devices
+  ✅ Settings synchronization
+  ✅ Encrypted API key storage
+  ✅ Web search capabilities
+
+Note: You can still use AI features offline, but web search requires authentication.
+```
+
+### 3. Interactive Picker
+```
+┌─ What would you like to do? ─┐
+│ > 🔑 Sign in with Google      │
+│   ❌ Exit                      │
+└───────────────────────────────┘
+```
+
+Users can navigate with arrow keys and press Enter to select.
+
+## User Choices
+
+### Option 1: Sign in with Google
+1. User selects "🔑 Sign in with Google"
+2. Screen clears and shows: "🔐 Opening browser for authentication..."
+3. Browser opens with Google OAuth flow
+4. User completes authentication in browser
+5. CLI receives session token
+6. Success message: "✅ You are now signed in and cloud sync is enabled!"
+7. Main CLI interface loads
+
+### Option 2: Exit
+1. User selects "❌ Exit"
+2. Screen clears
+3. Shows: "👋 Goodbye!"
+4. CLI exits gracefully
+
+## Returning Users
+
+When a user has an existing valid session:
+- Authentication screen is skipped
+- CLI loads directly to the main interface
+- User can start chatting immediately
+
+## Backend Unavailable
+
+If the backend API is not reachable:
+- Shows warning: "⚠️ Backend API is not reachable."
+- Continues in offline mode
+- User can still use AI features (except web search)
+
+## Session Management
+
+### Active Session
+- Session token stored in `~/.centaurus/session.json`
+- Valid for 30 days
+- Automatically refreshed on use
+
+### Logout
+- User types `/logout` command
+- Session cleared from local storage
+- CLI exits
+- Next start will show authentication screen again
+
+## Technical Details
+
+### Components Used
+- `AuthWelcomeScreen.tsx` - Main authentication welcome screen
+- `WelcomeBanner.tsx` - ASCII art banner
+- `SelectPrompt.tsx` - Interactive picker component
+
+### Authentication Flow
+1. Check if `apiClient.isAuthenticated()` returns true
+2. If not authenticated, check backend availability
+3. Render `AuthWelcomeScreen` component
+4. Wait for user selection
+5. Handle sign-in or exit accordingly
+
+### Error Handling
+- Backend unreachable → Continue in offline mode
+- Authentication failed → Exit with error message
+- User cancels → Exit gracefully
+
+## Benefits
+
+### User Experience
+- ✅ Beautiful, branded welcome screen
+- ✅ Clear explanation of features
+- ✅ Easy-to-use picker interface
+- ✅ No confusing Y/N prompts
+- ✅ Consistent with CLI UI theme
+
+### Developer Experience
+- ✅ Reusable components
+- ✅ Clean separation of concerns
+- ✅ Easy to modify or extend
+- ✅ Proper error handling
+
+## Future Enhancements
+
+Potential improvements:
+- Add "Learn More" option with detailed feature explanation
+- Show backend status (online/offline) in real-time
+- Add "Skip for now" option to continue in offline mode
+- Remember user preference for future sessions
+- Add animation to the banner

package/CONFIG_GUIDE.md

@@ -0,0 +1,255 @@
+# Centaurus CLI Configuration Guide
+
+## Overview
+
+The Centaurus CLI stores configuration in two places:
+1. **Environment variables** (`.env` file) - Backend API URL only
+2. **User config file** (`~/.centaurus/config.json`) - API keys and preferences
+
+## Initial Setup
+
+### 1. Backend API Configuration
+
+Create or update `.env` file in the CLI directory:
+
+```env
+BACKEND_API_URL=http://localhost:3000/api
+```
+
+For production, update to your backend URL:
+```env
+BACKEND_API_URL=https://api.yourapp.com/api
+```
+
+### 2. AI Provider API Keys
+
+Configure your API keys using slash commands in the CLI:
+
+```bash
+# Google AI (Gemini)
+/config set googleApiKey YOUR_GOOGLE_API_KEY
+
+# OpenRouter (Multiple AI models)
+/config set openrouterApiKey YOUR_OPENROUTER_API_KEY
+```
+
+**Get API Keys:**
+- Google AI Studio: https://makersuite.google.com/app/apikey
+- OpenRouter: https://openrouter.ai/keys
+
+## Configuration Commands
+
+### View Current Configuration
+
+```bash
+/config
+```
+
+Shows:
+- Current provider (google/openrouter)
+- Current model
+- API key status (configured or not)
+
+### Set API Keys
+
+```bash
+/config set googleApiKey YOUR_KEY_HERE
+/config set openrouterApiKey YOUR_KEY_HERE
+```
+
+Keys are:
+- Encrypted using machine-specific key
+- Stored in `~/.centaurus/config.json`
+- Never sent to backend (except for cloud sync)
+
+### Change Provider
+
+```bash
+/provider
+```
+
+Opens a picker to select:
+- `google` - Google Gemini models
+- `openrouter` - Multiple AI providers
+
+Or set directly:
+```bash
+/provider google
+/provider openrouter
+```
+
+### Change Model
+
+```bash
+/model
+```
+
+Opens a picker to select from available models:
+- gemini-2.5-flash
+- gemini-2.5-pro
+- gemini-2.0-flash-exp
+- gemini-2.0-flash-thinking-exp
+- gemini-1.5-pro
+- gemini-1.5-flash
+
+Or set directly:
+```bash
+/model gemini-2.5-flash
+```
+
+## Cloud Sync (Optional)
+
+### Sign In
+
+When you first run the CLI, you'll be prompted to sign in with Google for cloud sync features:
+
+**Cloud Sync Features:**
+- ✅ Conversation history across devices
+- ✅ Settings synchronization
+- ✅ Encrypted API key storage in cloud
+
+**Offline Mode:**
+- ✅ All AI features work
+- ✅ Local conversation history
+- ❌ No sync across devices
+- ❌ No web search (requires backend)
+
+### Sign Out
+
+```bash
+/logout
+```
+
+Clears your session and exits the CLI. You'll need to restart the CLI to continue using it in offline mode or sign in again.
+
+## Configuration File Location
+
+Your configuration is stored at:
+- **Windows**: `C:\Users\YourName\.centaurus\config.json`
+- **macOS/Linux**: `~/.centaurus/config.json`
+
+### Config File Structure
+
+```json
+{
+  "provider": "google",
+  "model": "gemini-2.5-flash",
+  "googleApiKey": "encrypted_key_here",
+  "openrouterApiKey": "encrypted_key_here",
+  "theme": "default",
+  "autoAccept": false
+}
+```
+
+**Note:** API keys are encrypted and cannot be read directly.
+
+## Web Search Configuration
+
+Web search is handled by the backend and requires:
+1. Authentication (sign in with Google)
+2. Backend server running with Serper API key
+
+**No client-side configuration needed!**
+
+The backend administrator configures the Serper API key server-side.
+
+## Troubleshooting
+
+### "API key not set" Error
+
+```bash
+# Check current config
+/config
+
+# Set the appropriate API key
+/config set googleApiKey YOUR_KEY
+```
+
+### "Authentication required" for Web Search
+
+Web search requires signing in:
+1. Restart the CLI
+2. Choose "Yes" when prompted to sign in
+3. Complete Google OAuth flow
+
+### "Backend API is not reachable"
+
+Check your `.env` file:
+```env
+BACKEND_API_URL=http://localhost:3000/api
+```
+
+Verify backend is running:
+```bash
+cd backend
+npm start
+```
+
+### Reset Configuration
+
+To start fresh, delete the config file:
+
+**Windows:**
+```cmd
+del %USERPROFILE%\.centaurus\config.json
+```
+
+**macOS/Linux:**
+```bash
+rm ~/.centaurus/config.json
+```
+
+Then restart the CLI and reconfigure.
+
+## Security Best Practices
+
+1. **Never commit `.env` files** - Add to `.gitignore`
+2. **Keep API keys private** - Don't share your config file
+3. **Use environment-specific URLs** - Different URLs for dev/prod
+4. **Rotate keys regularly** - Update keys periodically
+5. **Sign out on shared machines** - Use `/logout` command
+
+## Advanced Configuration
+
+### Multiple API Keys (Key Rotation)
+
+You can configure multiple API keys for automatic rotation:
+
+```bash
+/config set googleApiKey key1,key2,key3
+```
+
+The CLI will automatically rotate between keys to avoid rate limits.
+
+### Custom Backend URL
+
+For development or self-hosted backends:
+
+```env
+BACKEND_API_URL=http://localhost:3000/api
+```
+
+For production:
+
+```env
+BACKEND_API_URL=https://api.centaurus.app/api
+```
+
+## Getting Help
+
+```bash
+/help
+```
+
+Shows all available commands and their usage.
+
+## Next Steps
+
+1. Configure your API keys
+2. Choose your preferred provider and model
+3. Start chatting with the AI!
+4. (Optional) Sign in for cloud sync
+
+For more information, see:
+- [README.md](./README.md) - General CLI documentation
+- [COMMANDS.md](./COMMANDS.md) - Complete command reference

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Centaurus CLI Contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.