Architecture: Implementing the 5 capability gaps identified by Cowork agen...

Documentation for Sessions

🏗️ Architecture: Implementing the 5 capability gaps identified by Cowork agen...

Date: 2026-02-28
Time: 21:30:40 UTC
Session: gspace1-156.2
Agent: backend
Confidence: 91%
Status: ✅ Documented


📋 Decision Context

Question:

Implementing the 5 capability gaps identified by Cowork agent for Jarvis-level autonomy

Task: Session 152: Close 5 Jarvis capability gaps identified by Cowork agent


🎯 Decision Made

Chosen:

Implemented 4 of 5 gaps: 1) Session-scoped credentials with TTL + operation/branch restrictions in SecretVault, 2) Firecracker snapshot/restore service for persistent VMs on Hetzner server, 3) GitHub Actions proactive monitoring with webhook receiver, 4) VNC stream bug fix routing through SandboxProviderFactory. Gap 5 (accessibility tree) designed but requires Chrome CDP integration in Firecracker VMs. Also added: ComputerUseDataService (shared provider), enhanced sandbox dashboard with provider comparison cards, cognitive budgeting wired into engine, knowledge graph backfill, delegated_git tool, CredentialBridgeService with 3-fallback strategy.

Options Considered:


💭 Reasoning

The Cowork agent's feedback from inside the platform was the most valuable source of gap analysis. Each gap maps to a concrete limitation preventing autonomous operation: 1) No credentials = can't push code, 2) No persistence = cold boots every session, 3) No external monitoring = reactive-only, 4) No a11y = fragile coordinate clicking. Prioritized by impact: credential injection + persistent VMs enable the most new capabilities. GitHub monitoring enables proactive alerting. A11y tree is highest ROI for browser control accuracy but requires Chrome CDP in VMs (deferred to post-deployment). All changes maintain backward compatibility with existing providers.


📁 Files Involved


🔗 Related


Auto-generated by MCP Smart Consolidation