Architecture: Session 128: What is the critical next step to transform Vit...

Documentation for Sessions

🏗️ Architecture: Session 128: What is the critical next step to transform Vit...

Date: 2026-02-20
Time: 17:38:01 UTC
Session: gspace1-128.7
Agent: orchestrator
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Session 128: What is the critical next step to transform Vitto from chatbot to autonomous agent on WhatsApp?

Task: Not specified

🎯 Decision Made

Chosen:

Implement hybrid intent routing: classify messages as chat/command/complex-task and route to appropriate execution engine

Options Considered:

Improve prompt quality only
Switch to WhatsApp Business API (Meta direct)
Implement hybrid intent routing: classify messages as chat/command/complex-task and route to appropriate execution engine

💭 Reasoning

Vitto has ALL agent capabilities deployed on Railway (AgentLoopService with 20+ tools, TaskScheduler, WorkflowEngine, BrowserAgent, SubAgents) but the WhatsApp path bypasses them entirely — it only makes a single LLM call with no tools. The fix is routing: an intent classifier decides whether a message is conversation (fast path, 2-5s), command needing tools (agent loop, 5-30s), or complex task (full 4-phase pipeline, 1-5min). Plan documented in vitto-agent-not-chatbot.plan.md. Estimated: 1 session for Phase 1+2.

📁 Files Involved

No files specified

🔗 Related

Decision ID: dev_1771609081158_rvc39ze
Session: 128
Workspace: gspace1

Auto-generated by MCP Smart Consolidation