🏗️ Architecture: How to support IDE tool delegation from backend-vitto-api to...

Date: 2026-03-24
Time: 17:36:56 UTC
Session: gspace1-265.5
Agent: backend
Confidence: 90%
Status: ✅ Documented

📋 Decision Context

Question:

How to support IDE tool delegation from backend-vitto-api to VS Code extension?

Task: Not specified

🎯 Decision Made

Chosen:

ToolExecutionStrategy interface with LocalToolStrategy (wraps ToolRegistryService) and IdeToolStrategy (SSE push + Promise bridge). New POST /engine/agent-session streaming endpoint + POST /engine/agent-session/:sessionId/tool-result callback. Strategy pattern replaces hardcoded if/else in agent loop.

Options Considered:

• No alternatives documented

💭 Reasoning

The existing executeToolWithVmRouting() was a growing if/else chain. The SandboxedToolProxyService already proved external tool execution works. Rather than adding another else-if for IDE tools, introduced a ToolExecutionStrategy interface that abstracts execution location. Three implementations: LocalToolStrategy (in-process, fallback), VmToolStrategy (wraps existing VM proxy), IdeToolStrategy (novel SSE+POST bridge). The streaming POST pattern matches what the extension already expects — it reads SSE from the POST response body, not a separate GET. AgentLoopOptions gains toolStrategies array; backward compatible.

📁 Files Involved

• APIs/backend-vitto-api/src/app/tools/strategies/tool-execution-strategy.ts
• APIs/backend-vitto-api/src/app/tools/strategies/ide-tool.strategy.ts
• APIs/backend-vitto-api/src/app/tools/strategies/local-tool.strategy.ts
• APIs/backend-vitto-api/src/app/engine/agent-loop.service.ts
• APIs/backend-vitto-api/src/app/engine/vitto-engine.service.ts
• APIs/backend-vitto-api/src/app/engine/vitto.controller.ts

🔗 Related

• Decision ID: dev_1774373816182_6qf3fsc
• Session: 265
• Workspace: gspace1

Auto-generated by MCP Smart Consolidation