feat: New Session Page w/ one touch Profiles, adds z.ai / deepseek / microsoft AI Backend Support #272

.envrc.example

@@ -0,0 +1,17 @@
+# Happy CLI Development Environment
+#
+# This file is for direnv users who want automatic environment switching
+# when entering this directory.
+#
+# Setup:
+#   1. Install direnv: https://direnv.net/
+#   2. Copy this file: cp .envrc.example .envrc
+#   3. Run: direnv allow
+#
+# The .envrc file is gitignored, so each developer can customize it.
+
+export HAPPY_HOME_DIR="$HOME/.happy-dev"
+export HAPPY_VARIANT="dev"
+export HAPPY_SERVER_URL="${HAPPY_SERVER_URL:-https://api.cluster-fluster.com}"
+
+echo "🔧 DEV environment activated (data: $HAPPY_HOME_DIR)"

.gitignore

@@ -17,12 +17,17 @@ pnpm-lock.yaml
 # Environment variables
 .env
 .env*.local
+.envrc
 
 # Claude code session level settings
 .claude/settings.local.json
 
-# Local installation
+# Local installation and data directories
 .happy/
+.happy-dev/
 
 **/*.log
-.release-notes-temp.md
+.release-notes-temp.md
+
+# Git worktrees for isolated branch work
+.worktrees/

CONTRIBUTING.md

@@ -0,0 +1,333 @@
+# Contributing to Happy CLI
+
+## Prerequisites
+
+- Node.js >= 20.0.0
+- Yarn (`npm install -g yarn`)
+- Git
+- Claude CLI installed and logged in (`claude` command available in PATH)
+
+## Getting Started
+
+```bash
+git clone https://github.com/slopus/happy-cli.git
+cd happy-cli
+yarn install
+yarn build
+```
+
+## Development Commands
+
+### Global `happy-dev` Command
+
+Create a global `happy-dev` command that runs your local development build:
+
+```bash
+yarn link:dev      # Create happy-dev symlink
+yarn unlink:dev    # Remove happy-dev symlink
+```
+
+This creates a `happy-dev` command in your PATH pointing to your local build, while leaving any npm-installed `happy` command untouched.
+
+| Command | Runs |
+|---------|------|
+| `happy` | Stable npm version (from `npm install -g happy-coder`) |
+| `happy-dev` | Local development version (from this repo) |
+
+**Note:** Run `yarn build` before `yarn link:dev` to ensure the binary exists.
+
+### Build Commands
+
+```bash
+yarn build         # Build the project
+yarn typecheck     # TypeScript type checking
+yarn test          # Run tests
+yarn dev           # Run without building (uses tsx)
+```
+
+## Stable vs Dev Data Isolation
+
+The CLI supports running stable and development versions side-by-side with completely isolated data.
+
+### Initial Setup (Once)
+
+```bash
+npm run setup:dev
+```
+
+This creates:
+- `~/.happy/` - Stable version data (production-ready)
+- `~/.happy-dev/` - Development version data (for testing changes)
+
+### Daily Usage
+
+**Stable (production-ready):**
+```bash
+npm run stable:daemon:start
+```
+
+**Development (testing changes):**
+```bash
+npm run dev:daemon:start
+```
+
+## Visual Indicators
+
+You'll always see which version you're using:
+- `✅ STABLE MODE - Data: ~/.happy`
+- `🔧 DEV MODE - Data: ~/.happy-dev`
+
+## Common Tasks
+
+### Authentication
+
+```bash
+# Authenticate stable version
+npm run stable auth login
+
+# Authenticate dev version (can use same or different account)
+npm run dev auth login
+
+# Logout
+npm run stable auth logout
+npm run dev auth logout
+```
+
+### Daemon Management
+
+```bash
+# Check status of both
+npm run stable:daemon:status
+npm run dev:daemon:status
+
+# Stop both
+npm run stable:daemon:stop
+npm run dev:daemon:stop
+
+# Start both simultaneously
+npm run stable:daemon:start && npm run dev:daemon:start
+```
+
+### Running Any Command
+
+```bash
+# Stable version
+npm run stable <command> [args...]
+npm run stable notify "Test message"
+npm run stable doctor
+
+# Dev version
+npm run dev:variant <command> [args...]
+npm run dev:variant notify "Test message"
+npm run dev:variant doctor
+```
+
+## Data Isolation
+
+Both versions maintain complete separation:
+
+| Aspect | Stable | Development |
+|--------|--------|-------------|
+| Data Directory | `~/.happy/` | `~/.happy-dev/` |
+| Settings | `~/.happy/settings.json` | `~/.happy-dev/settings.json` |
+| Auth Keys | `~/.happy/access.key` | `~/.happy-dev/access.key` |
+| Daemon State | `~/.happy/daemon.state.json` | `~/.happy-dev/daemon.state.json` |
+| Logs | `~/.happy/logs/` | `~/.happy-dev/logs/` |
+
+**No conflicts!** Both can run simultaneously with separate:
+- Authentication sessions
+- Server connections
+- Daemon processes
+- Session histories
+- Configuration settings
+
+## Advanced: direnv Auto-Switching
+
+For automatic environment switching when entering directories:
+
+1. Install [direnv](https://direnv.net/):
+   ```bash
+   # macOS
+   brew install direnv
+
+   # Add to your shell (bash/zsh)
+   eval "$(direnv hook bash)"  # or zsh
+   ```
+
+2. Setup direnv for this project:
+   ```bash
+   cp .envrc.example .envrc
+   direnv allow
+   ```
+
+3. Now `cd` into the directory automatically sets `HAPPY_VARIANT=dev`!
+
+## Troubleshooting
+
+### Commands not working?
+```bash
+npm install
+```
+
+### Permission denied on scripts?
+```bash
+chmod +x scripts/*.cjs
+```
+
+### Data directories not created?
+```bash
+npm run setup:dev
+```
+
+### Both daemons won't start?
+Check port conflicts - each daemon needs its own port. The dev daemon will automatically use a different port from stable.
+
+### How do I check which version is running?
+Look for the visual indicator:
+- `✅ STABLE MODE` = stable version
+- `🔧 DEV MODE` = development version
+
+Or check the daemon status:
+```bash
+npm run stable:daemon:status   # Shows ~/.happy/ data location
+npm run dev:daemon:status       # Shows ~/.happy-dev/ data location
+```
+
+### `yarn link:dev` fails with permission denied?
+```bash
+sudo yarn link:dev
+```
+
+### `happy-dev` command not found after linking?
+- Ensure your global npm bin is in PATH: `npm bin -g`
+- Try opening a new terminal window
+- Check the symlink was created: `ls -la $(npm bin -g)/happy-dev`
+
+## Tips
+
+1. **Use stable for production work** - Your tested, reliable version
+2. **Use dev for testing changes** - Test new features without breaking your workflow
+3. **Run both simultaneously** - Compare behavior side-by-side
+4. **Different accounts** - Use different Happy accounts for dev/stable if needed
+5. **Check logs** - Logs are separated: `~/.happy/logs/` vs `~/.happy-dev/logs/`
+
+## Example Workflow
+
+```bash
+# Initial setup (once)
+yarn install
+yarn build
+yarn link:dev
+npm run setup:dev
+
+# Authenticate both
+npm run stable auth login
+npm run dev:variant auth login
+
+# Start both daemons
+npm run stable:daemon:start
+npm run dev:daemon:start
+
+# Do your development work...
+# Edit code, build, test with dev version
+
+# When ready, update stable version
+npm run stable:daemon:stop
+git pull  # or your deployment process
+npm run stable:daemon:start
+
+# Dev continues running unaffected!
+```
+
+## How It Works
+
+The system uses the built-in `HAPPY_HOME_DIR` environment variable to separate data:
+
+- **Stable scripts** set: `HAPPY_HOME_DIR=~/.happy`
+- **Dev scripts** set: `HAPPY_HOME_DIR=~/.happy-dev`
+
+Everything else (auth, sessions, logs, daemon) automatically follows the `HAPPY_HOME_DIR` setting.
+
+Cross-platform via Node.js - works identically on Windows, macOS, and Linux!
+
+## Testing Profile Sync Between GUI and CLI
+
+Profile synchronization ensures AI backend configurations created in the Happy mobile/web GUI work seamlessly with the CLI daemon.
+
+### Profile Schema Validation
+
+The profile schema is defined in both repositories:
+- **GUI:** `sources/sync/settings.ts` (AIBackendProfileSchema)
+- **CLI:** `src/persistence.ts` (AIBackendProfileSchema)
+
+**Critical:** These schemas MUST stay in sync to prevent sync failures.
+
+### Testing Profile Sync
+
+1. **Create profile in GUI:**
+   ```
+   - Open Happy mobile/web app
+   - Settings → AI Backend Profiles
+   - Create new profile with custom environment variables
+   - Note the profile ID
+   ```
+
+2. **Verify CLI receives profile:**
+   ```bash
+   # Start daemon with dev variant
+   npm run dev:daemon:start
+
+   # Check daemon logs
+   tail -f ~/.happy-dev/logs/*.log | grep -i profile
+   ```
+
+3. **Test profile-based session spawning:**
+   ```bash
+   # From GUI: Start new session with custom profile
+   # Check CLI daemon logs for:
+   # - "Loaded X environment variables from profile"
+   # - "Using GUI-provided profile environment variables"
+   ```
+
+4. **Verify environment variable expansion:**
+   ```bash
+   # If profile uses ${VAR} references:
+   # - Set reference var in daemon environment: export Z_AI_AUTH_TOKEN="sk-..."
+   # - Start session from GUI
+   # - Verify daemon logs show expansion: "${Z_AI_AUTH_TOKEN}" → "sk-..."
+   ```
+
+### Testing Schema Compatibility
+
+When modifying profile schemas:
+
+1. **Update both repositories** - Never update one without the other
+2. **Test migration** - Existing profiles should migrate gracefully
+3. **Version bump** - Update `CURRENT_PROFILE_VERSION` if schema changes
+4. **Test validation** - Invalid profiles should be caught with clear errors
+
+### Common Issues
+
+**"Invalid profile" warnings in logs:**
+- Check profile has valid UUID (not timestamp)
+- Verify environment variable names match regex: `^[A-Z_][A-Z0-9_]*$`
+- Ensure compatibility.claude or compatibility.codex is true
+
+**Environment variables not expanding:**
+- Reference variable must be set in daemon's process.env
+- Check daemon logs for expansion warnings
+- Verify no typos in ${VAR} references
+
+## Publishing to npm
+
+Maintainers can publish new versions:
+
+```bash
+yarn release       # Interactive version bump, changelog, publish
+```
+
+This runs tests, builds, and publishes to npm. The published package includes:
+- `happy` - Main CLI command
+- `happy-mcp` - MCP bridge command
+
+**Note:** `happy-dev` is intentionally excluded from the npm package - it's for local development only.

README.md

@@ -47,6 +47,10 @@ This will:
 - `HAPPY_DISABLE_CAFFEINATE` - Disable macOS sleep prevention (set to `true`, `1`, or `yes`)
 - `HAPPY_EXPERIMENTAL` - Enable experimental features (set to `true`, `1`, or `yes`)
 
+## Contributing
+
+Interested in contributing? See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup and guidelines.
+
 ## Requirements
 
 - Node.js >= 20.0.0