[Feature]: Typed outputs for coding agents

[homanp]

Feature Description

Users want to know what the expected output of the coding agents are in streaming and non-streaming. We should add output types to the response objects

[homanp]

@claude

Research the internet of the return of each agent type we have, eg. claude code, code, etc. etc.

Add typed output for the streaming and the executeCommand statement. Research the users questions here #227

[claude]

Claude finished @homanp's task —— View job • claude/issue-230-20250913-2019 • Create PR ➔

---

Typed outputs for coding agents complete! ✅

• Read repository setup instructions (CLAUDE.md)
• Research issue [Feature]: Issues with Streaming Update in e2b when using opencode: mixed messages and non-real streaming output #227 for user requirements
• Explore codebase to identify agent types and their current outputs
• Analyze existing type definitions
• Create unified streaming output types
• Create unified executeCommand return types
• Update base agent class to use typed responses
• Update individual agent implementations
• Export the new types from the main index
• Test the implementation
• Commit and push changes

Implementation Summary

I've successfully added comprehensive typed outputs for all coding agents in the vibekit SDK. Here's what was implemented:

🔧 New Unified Types:

• StreamingMessage: Structured interface for streaming data with type ('start' | 'git' | 'end'), sandbox_id, and output properties
• StreamCallbacks: Unified callback interface that accepts both StreamingMessage objects and raw strings
• AgentResponse: Base response type with exitCode, stdout, stderr, sandboxId, patch, branchName, commitSha
• ExecuteCommandResponse: Specific type extending AgentResponse for executeCommand operations
• ExecuteCommandOptions: Typed options for command execution with timeoutMs, background, callbacks, branch

🔄 Agent Type Consolidation:
All agent-specific response types (CodexResponse, ClaudeResponse, GeminiResponse, GrokResponse, OpenCodeResponse) now extend the unified AgentResponse interface, eliminating duplication while maintaining backward compatibility.

📡 Enhanced Streaming:

• Replaced raw JSON strings like {"type": "start", "sandbox_id": "..."} with typed StreamingMessage objects
• All streaming callbacks now provide structured data instead of unparsed strings
• Improved parsing in StreamingBuffer class with automatic JSON parsing and fallback to raw strings

📦 Public API:
Exported all new types from the main SDK index so developers can import and use them for type safety.

✅ Backward Compatibility:
All existing agent-specific types remain available and functional, they just extend the new unified interfaces.

Benefits for Users:

1. IDE Support: Full autocompletion and IntelliSense for streaming messages and responses
2. Type Safety: Compile-time checking prevents runtime errors from malformed data
3. Consistent API: All agents now have identical response structures
4. Better DX: Clear type definitions make the SDK easier to understand and use