lovelace chat

lovelace chat [options]

$ lovelace chat

🤖 Lovelace CLI v1.0.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Connected to: claude-sonnet-4-5
Workspace: my-project
Project: /Users/dev/my-project

Type your message or use slash commands:
  /help    Show available commands
  /context Add files to conversation
  /clear   Clear conversation history
  /exit    End session

You: How does authentication work in this codebase?

🤖 I can see you're working on a Next.js project with Auth. Let me analyze
   your authentication setup.

   Based on the code in `src/app/api/auth/[...auth]/route.ts`, your auth system uses:

   1. **OAuth Providers**: Google and GitHub OAuth
   2. **Session Strategy**: JWT-based sessions
   3. **Callbacks**: Custom JWT and session callbacks for user metadata

   Would you like me to explain any specific part in more detail?

You: Yes, explain the session callback

🤖 The session callback in your setup does two things:

   [Detailed explanation with code references]

You: /exit

✓ Session saved: session_abc123

$ lovelace chat

You: Help me add authentication to my app

🤖 I'd be happy to help! To give you the best guidance, let me ask a few questions:

   1. What framework are you using?
      • Next.js
      • Express.js
      • Other

   2. What type of authentication do you need?
      • Email/password
      • OAuth (Google, GitHub, etc.)
      • Passkeys
      • Multiple methods

   3. Do you have a database set up?
      • Yes (which one?)
      • Not yet

You: Next.js 14 with App Router, OAuth with Google and GitHub, using Prisma with PostgreSQL

🤖 Perfect! I'll help you implement OAuth authentication with Google and GitHub using:
   ✓ Next.js 14 App Router
   ✓ Auth v5 (Auth.js)
   ✓ Prisma with PostgreSQL

   Let's start step-by-step. First, would you like me to:
   1. Show you the complete setup
   2. Walk through it step-by-step
   3. Explain the architecture first

You: 2

🤖 Great! Here's our plan:

   **Step 1**: Install dependencies
   **Step 2**: Configure Auth
   **Step 3**: Set up OAuth providers
   **Step 4**: Create Prisma schema
   **Step 5**: Add API routes
   **Step 6**: Create login UI

   Ready to start with Step 1?

You: yes

🤖 **Step 1: Install Dependencies**

   Run these commands:
   [Installation instructions with explanations]

$ lovelace chat

You: /help

Available Commands:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Session Control:
  /exit          End chat session
  /clear         Clear conversation history
  /save          Save current session
  /resume <id>   Resume previous session

Context Management:
  /context <path>    Add file or directory to context
  /context list      Show current context
  /context clear     Clear all context

Settings:
  /model <name>      Switch AI model
  /provider <name>   Switch AI provider

You: /context src/auth/login.ts

✓ Added to context: src/auth/login.ts (234 lines)

Current context (1 file, 234 lines):
  • src/auth/login.ts

You: Review this code for security issues

🤖 I've reviewed your login.ts file. Here are the security concerns I found:

   1. **Critical**: Password hashing missing
      Line 45: Passwords stored in plain text

      Fix:
      ```typescript
      import bcrypt from 'bcrypt';
      const hashedPassword = await bcrypt.hash(password, 10);
      ```

   [Additional security feedback...]

$ lovelace chat --load session_abc123

🤖 Resuming session: Authentication implementation discussion
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Last message: "Would you like me to explain the session callback?"

Loaded context:
  • src/auth/login.ts
  • src/auth/register.ts
  • src/auth/session.ts

You: Yes, explain the session callback

🤖 [Continues from where you left off...]

$ lovelace chat --provider openai --model gpt-4

🤖 Lovelace CLI v1.0.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Connected to: gpt-4
Provider: OpenAI
Workspace: my-project

You: Help me optimize this SQL query
[...]

$ lovelace chat --provider ollama --model llama2

🤖 Lovelace CLI v1.0.0
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Connected to: llama2 (local)
Provider: Ollama
Workspace: my-project
Note: Using local model - no API calls

You: Explain this function
[...]

$ lovelace chat

You: /context src/api/user-service.ts

You: Review this code for potential issues and improvements

🤖 I've analyzed your user service. Here's my review:

   **Issues Found:**
   1. Missing input validation (lines 23-45)
   2. No error handling for database failures
   3. Potential race condition in user creation

   **Suggested Improvements:**
   1. Add Zod schemas for validation
   2. Implement retry logic for transient failures
   3. Use database transactions for user creation

   Would you like me to show code examples for any of these?

You: I'm getting this error: "Cannot read property 'id' of undefined"

🤖 This error typically occurs when you're trying to access a property on a value
   that's undefined. To help you debug:

   1. Where is this error occurring? (file and line number)
   2. What operation were you performing?
   3. Can you share the relevant code?

You: It's in src/api/auth.ts line 67 when trying to get user.id

🤖 Let me see that code:

You: /context src/api/auth.ts

🤖 I can see the issue. On line 67, you're accessing `user.id`, but the user
   might be null if the database query doesn't find a match.

   Here's the fix:
   [Code example with null checking...]

You: Explain how React Server Components work

🤖 React Server Components (RSC) are a new paradigm in React that allows components
   to render on the server and stream to the client. Here's how they work:

   **Key Concepts:**
   1. Server-only execution - No JavaScript shipped to client
   2. Direct database access - No API routes needed
   3. Automatic code splitting - Better performance

   Would you like me to:
   - Show practical examples
   - Explain the difference from traditional SSR
   - Demonstrate with your Next.js project

❌ "Fix this code"
✅ "Review user-service.ts authentication logic for SQL injection vulnerabilities"

❌ "How should I structure this?"
✅ "/context src/architecture.md
    How should I structure the new payment service based on our existing architecture?"

Start broad → Get specific → Refine based on responses

# Add only relevant files
/context src/auth/login.ts

# Add related files when discussion evolves
/context src/auth/session.ts
/context src/types/user.ts

/context clear
/context src/api/posts.ts

/save "Authentication implementation discussion"

lovelace chat --load session_abc123