Problems Addressed

Issue #1: Each Prompt Created New Conversation

What Was Happening:

• User sends Prompt #1 → Conversation #1 created with 2 messages (Q+A)
• User sends Prompt #2 → Conversation #2 created with 2 messages (Q+A)
• User sends Prompt #3 → Conversation #3 created with 2 messages (Q+A)
• Result: 3 separate conversations instead of 1 conversation with 3 Q&A pairs

Impact:

• Users cannot have multi-turn conversations
• Each question is isolated from previous context
• Conversation list becomes cluttered with many single-exchange conversations
• No way to continue a conversation (all are closed/new)

Issue #2: Conversations List Shows Only Numbers

What Was Happening:

• Conversations list shows ID numbers without meaningful content
• Preview text doesn't clearly indicate what the conversation is about
• Users can't identify conversations at a glance

Example of Old View:

Conversation #1234
Status: active
Messages: 2
Created: 2025-12-27 01:15
[Preview text - possibly just AI response]
        

Example of New View:

What is machine learning?
Status: active
Messages: 4
Created: 2025-12-27 01:15
Q: What is machine learning? | A: Machine learning is a subset of...
        

Solutions Implemented

Fix #1: Support Multi-Turn Conversations

Backend Changes (/Comserv/lib/Comserv/Controller/AI.pm)

my $conversation_id = $json_data->{conversation_id} || 
                   $c->request->params->{conversation_id};

unless ($final_conversation_id) {
    # Create new conversation (first message)
    my $conversation = $schema->resultset('AiConversation')->create({...});
    $final_conversation_id = $conversation->id;
} else {
    # Reuse existing conversation (follow-up message)
    # Just log and continue
}

# Both user and AI messages use the SAME conversation_id
$schema->resultset('AiMessage')->create({
    conversation_id => $final_conversation_id,
    role => 'user',
    content => $prompt,
    ...
});

$schema->resultset('AiMessage')->create({
    conversation_id => $final_conversation_id,
    role => 'assistant',
    content => $ai_response,
    ...
});

Frontend Changes (/Comserv/root/ai/index.tt)

let currentConversationId = null;

const requestBody = {
    prompt: prompt,
    model: selectedModel,
    history: conversationHistory.slice(-10)
};

if (currentConversationId) {
    requestBody.conversation_id = currentConversationId;
}

if (data.conversation_id) {
    currentConversationId = data.conversation_id;
    // Display it and show "saved" notification
}

document.getElementById('conversation-id-display').textContent = 
    data.conversation_id;
document.getElementById('conversation-info').style.display = 'block';

Fix #2: Improve Conversation Preview

Backend Changes (/Comserv/lib/Comserv/Controller/AI.pm)

Updated the conversations action to generate better preview text:

# Get all messages for conversation
my @messages = $conv->ai_messages->all;

# Find first user message (question) and AI response (answer)
foreach my $msg (@messages) {
    if ($msg->role eq 'user' && !$user_msg) {
        $user_msg = $msg->content;
    }
    if ($msg->role eq 'assistant' && !$ai_msg) {
        $ai_msg = $msg->content;
    }
}

# Create readable preview
$preview = "Q: " . substr($user_msg, 0, 60) . "...";
$preview .= " | A: " . substr($ai_msg, 0, 40) . "...";
            

Result Format:

Q: What is the difference between AI and machine learning? | A: AI is the broader field, while machine learning is...
        

User Experience Flow

How It Works Now

Technical Details

Files Modified

Database Impact

• ai_conversations: Fewer new rows (reused across multi-turn)
• ai_messages: More messages per conversation (2 per exchange)
• Result: Better organized conversation history with context preserved

API Changes

/ai/chat Request (NEW):

{
  "prompt": "What is Python?",
  "model": "qwen2.5-coder:1.5b-base",
  "history": [...],
  "conversation_id": 42  // ← NEW: Include for follow-up
}

/ai/chat Response (SAME):

{
  "success": true,
  "response": "Python is a high-level programming language...",
  "model": "qwen2.5-coder:1.5b-base",
  "conversation_id": 42  // ← Still returned (now reused)
}

Testing the Fix

Verification Steps

1. Start fresh conversation:
   • Go to /ai
   • Type first prompt and send
   • Verify: "Conversation #[N] saved" appears
   • Verify: "Conversation #[N]" shows in header
2. Ask follow-up question:
   • Type another prompt in same chat
   • Send it
   • Verify: NO new "saved" notification (same conversation)
   • Verify: Conversation ID in header stays the same
3. Check conversation list:
   • Click "Conversations" button
   • Verify: Only ONE conversation shows (not multiple)
   • Verify: Preview shows "Q: [first question] | A: [answer snippet]"
   • Verify: Message count shows "4" (2 Q&A pairs)
4. View conversation details:
   • Click "View" on conversation
   • Verify: All 4 messages show (2 from user, 2 from AI)
   • Verify: Messages appear in order (chronological)
5. Test persistence:
   • Go back to /ai
   • Do NOT select the conversation
   • Start new conversation (different topic)
   • Verify: NEW conversation_id appears in header
   • Check conversations list
   • Verify: BOTH conversations exist with different previews

Expected Results

Related Fixes

• Dec 26: Fixed DBSchemaManager to auto-create AI Chat tables
• Dec 27 (Part 1): Added conversation saving to /ai/chat endpoint
• Dec 27 (Part 2, this): Fixed multi-turn conversations and improved previews