🏗️ Architecture: How should WhatsApp Vitto evolve from chatbot to autonomous ...

Date: 2026-02-20
Time: 17:18:42 UTC
Session: gspace1-128.4
Agent: orchestrator
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

How should WhatsApp Vitto evolve from chatbot to autonomous agent like Chad Nicely's OpenClaw Pacino?

Task: Not specified

🎯 Decision Made

Chosen:

Hybrid routing — classify intent, route to fast path (chat) or agent loop (commands) or full pipeline (complex tasks)

Options Considered:

1. Stay as chatbot — just improve prompt quality
2. Build from scratch — new agent architecture for channels
3. Hybrid routing — classify intent, route to fast path (chat) or agent loop (commands) or full pipeline (complex tasks)

💭 Reasoning

Vitto already has ALL agent capabilities deployed (AgentLoopService, 20+ tools, TaskScheduler, WorkflowEngine, BrowserAgent, SubAgents). The WhatsApp path just bypasses them. The fix is routing: an intent classifier decides whether a message is conversation (fast path), command (agent loop with tools), or complex task (full 4-phase pipeline). This matches Chad's Pacino pattern — conversational when chatting, but takes real actions when commanded. No new services needed, just wiring.

📁 Files Involved

• No files specified

🔗 Related

• Decision ID: dev_1771607922234_p2fbae4
• Session: 128
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation