🐛 Bugfix: Session 181: Why was Vitto blind to the user's current page ...

Date: 2026-03-05
Time: 21:53:24 UTC
Session: gspace1-180.2
Agent: angular
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Session 181: Why was Vitto blind to the user's current page in web chat?

Task: Fix Vitto chat intelligence gaps

🎯 Decision Made

Chosen:

Fixed 3 bugs: (1) pageContext not sent in sendMessageViaVitto POST body, (2) buildWebSystemPrompt missing all intelligence (semantic recall, learning, awareness), (3) browser_screenshot taking blank server-side screenshots instead of user's screen

Options Considered:

• No alternatives documented

💭 Reasoning

sendMessageViaVitto sent {message, spaceId} but omitted pageContext — the backend accepted it but frontend never sent it. buildWebSystemPrompt was a stripped-down version missing semantic recall, learning intelligence, awareness hub, memory dedup, and personality rules that the WhatsApp channel had. browser_screenshot used server-side Playwright with no page loaded.

📁 Files Involved

• libs/libs-ai/vitto-chat/src/lib/services/vitto-chat-engine.service.ts
• APIs/backend-vitto-api/src/app/engine/context-assembly.service.ts
• APIs/backend-vitto-api/src/app/tools/tool-registry.service.ts
• APIs/backend-vitto-api/src/app/engine/agent-loop.service.ts
• APIs/backend-vitto-api/src/app/engine/vitto-engine.service.ts

🔗 Related

• Decision ID: dev_1772747604950_8e1hil0
• Session: 180
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation