Commit Graph

11 Commits

  • fix(auth): use correct model config format (object, not string)
    OpenClaw expects agents.defaults.model as { primary: "provider/model" }
    not a plain string. The previous code wrote a string which caused:
    "agents.defaults.model: Invalid input: expected object, received string"
  • fix(auth): configure OpenClaw default model when saving provider
    - Add setOpenClawDefaultModel() to write the correct model to
      ~/.openclaw/openclaw.json based on the selected provider
    - Maps: openrouter -> openrouter/anthropic/claude-sonnet-4,
      anthropic -> anthropic/claude-sonnet-4, etc.
    - Call setOpenClawDefaultModel on provider:save IPC handler
    - Fixes "No API key found for provider anthropic" when user
      configured OpenRouter (wrong default model was being used)
  • feat(chat): write API keys to OpenClaw and embed Control UI for chat
    Part 1: API Key Integration
    - Create electron/utils/openclaw-auth.ts to write keys to
      ~/.openclaw/agents/main/agent/auth-profiles.json
    - Update provider:save and provider:setApiKey IPC handlers to
      persist keys to OpenClaw auth-profiles alongside ClawX storage
    - Save API key to OpenClaw on successful validation in Setup wizard
    - Pass provider API keys as environment variables when starting
      the Gateway process (ANTHROPIC_API_KEY, OPENROUTER_API_KEY, etc.)
    
    Part 2: Embed OpenClaw Control UI for Chat
    - Replace custom Chat UI with <webview> embedding the Gateway's
      built-in Control UI at http://127.0.0.1:{port}/?token={token}
    - Add gateway:getControlUiUrl IPC handler to provide tokenized URL
    - Enable webviewTag in Electron BrowserWindow preferences
    - Override X-Frame-Options/CSP headers to allow webview embedding
    - Suppress noisy control-ui token_mismatch stderr messages
    - Add loading/error states for the embedded webview
    
    This fixes the "No API key found for provider" error and replaces
    the buggy custom chat implementation with OpenClaw's battle-tested
    Control UI.
  • feat(providers): implement real API key validation with OpenRouter support
    - Replace mock API key validation with actual API calls to verify keys
    - Add validateApiKeyWithProvider() with provider-specific implementations
    - Support Anthropic, OpenAI, Google, and OpenRouter validation
    - Add OpenRouter as a new provider option in setup wizard and settings
    - Fix setup page to call real validation instead of mock length check
    - Allow validation during setup before provider is saved
    - Return user-friendly error messages instead of raw API errors
  • fix(gateway): use GitHub URL for OpenClaw submodule and add token auth
    - Change submodule URL from local path to https://github.com/openclaw/openclaw.git
    - Checkout stable version v2026.2.3
    - Add auto-generated gateway token (clawx-xxx) stored in electron-store
    - Pass token via --token argument and OPENCLAW_GATEWAY_TOKEN env var
    - Include token in WebSocket URL for authentication
    - Add --dev and --allow-unconfigured flags for first-time setup
  • feat(gateway): integrate OpenClaw as git submodule
    - Add OpenClaw as git submodule at ./openclaw/
    - Update GatewayManager to start gateway from submodule path
    - Support both production (dist) and development (pnpm dev) modes
    - Add IPC handler for OpenClaw status check
    - Update Setup wizard to check real OpenClaw submodule status
    - Configure electron-builder to include submodule in packaged app
    - Add npm scripts for submodule management:
      - postinstall: auto-init submodule
      - openclaw:init: initialize and install dependencies
      - openclaw:install: install dependencies only
      - openclaw:build: build OpenClaw
      - openclaw:update: update to latest version
  • feat(channels): implement channel connection flows with multi-platform support
    - Add comprehensive Channels page with connection statistics and status display
    - Implement AddChannelDialog with type-specific connection flows:
      - QR code-based connection for WhatsApp/WeChat
      - Token-based connection for Telegram/Discord/Slack
    - Enhance channels store with addChannel, deleteChannel, and requestQrCode actions
    - Update electron-store usage to dynamic imports for ESM compatibility
    - Add channel connection instructions and documentation links
  • feat(providers): implement secure API key storage and provider management
    Add complete provider configuration system with the following features:
    
    - Secure API key storage using Electron's safeStorage encryption
    - Provider CRUD operations with IPC handlers
    - Lazy-loaded electron-store for ESM compatibility
    - Provider settings UI component with add/edit/delete functionality
    - API key masking for display (shows first/last 4 chars)
    - Basic API key format validation per provider type
    - Default provider selection
    - Provider enable/disable toggle
    
    New files:
    - electron/utils/secure-storage.ts: Encrypted key storage and provider config
    - src/stores/providers.ts: Zustand store for provider state
    - src/components/settings/ProvidersSettings.tsx: Provider management UI
  • feat(core): initialize project skeleton with Electron + React + TypeScript
    Set up the complete project foundation for ClawX, a graphical AI assistant:
    
    - Electron main process with IPC handlers, menu, tray, and gateway management
    - React renderer with routing, layout components, and page scaffolding
    - Zustand state management for gateway, settings, channels, skills, chat, and cron
    - shadcn/ui components with Tailwind CSS and CSS variable theming
    - Build tooling with Vite, electron-builder, and TypeScript configuration
    - Testing setup with Vitest and Playwright
    - Development configurations (ESLint, Prettier, gitignore, env example)