┌────────────────────────────────────────────────────────────────────────┐
│                        📊 TELEMETRY COMPRESSION BOARD                  │
├───────────────────┬──────────────────────┬─────────────────────────────┤
│ 📦 FOOTPRINT       │ 🚀 PERFORMANCE       │ 💥 STABILITY & ERRORS       │
│ • Monorepo / Core │ • Workflow Engine    │ • Schema validation         │
│ • 146 directories │ • Resumable stream   │ • Guardrail policies        │
└───────────────────┴──────────────────────┴─────────────────────────────┘

📈 PERFORMANCE

  • Resumable Streaming: Persistent connection state -> Stream recovery on client reconnect.
  • Workflow Chain Execution: Declarative multi-step routing -> Suspends & resumes without process state loss.
  • Supervisor-to-Sub-Agent Routing: Coordinated dispatch latency -> Direct path routing under supervisor runtime.

📦 FOOTPRINT

  • @voltagent/core: Core TS Framework runtime (Memory, RAG, Guardrails, Tools, MCP, Voice).
  • @voltagent/mcp-docs-server: Context provider for IDE extensions (Claude, Cursor, Windsurf).
  • examples/: 30+ integration templates (Airtable, Slack, WhatsApp, Bedrock, Anthropic, Chroma).
  • website/: Docusaurus-based documentation, evaluations, recipes, and prompt engineering docs.

💥 STABILITY

  • Guardrail Boundary Interception: Input/Output validation policies -> Runtime exception safety.
  • Zod-Typed Tools: Strongly-typed tool registry schemas -> Schema drift prevention.
  • Vitest Test Workspace: Unit & integration coverage -> Workspace-wide test execution stability.

🚨 GOTCHAS

  • VoltOps Console Sync: Local servers (defaulting to port 3141) require active internet connectivity to communicate trace metrics to console.voltagent.dev.
  • Stateful Suspensions: Long-running workflows that leverage suspend require a configured persistent storage adapter (e.g. LibSQLMemoryAdapter) to survive server restarts.