Skip to content

Latest commit

 

History

History
195 lines (150 loc) · 7 KB

File metadata and controls

195 lines (150 loc) · 7 KB

OpenCode Agent System Gap Analysis

Executive Summary

This analysis compares OpenCode's agent system against competitors Crush (Charm) and AmpCode (SourceGraph). OpenCode has a solid foundation but lags in key areas like autonomous reasoning, workflow orchestration, and agent specialization.

Agent System Locations

OpenCode Agent System

  • Core Files: packages/opencode/src/agent/agent.ts, packages/opencode/src/acp/agent.ts
  • Permission System: packages/opencode/src/permission/index.ts
  • Tool Registry: packages/opencode/src/tool/registry.ts
  • Session Management: packages/opencode/src/session/
  • Agent Prompts: packages/opencode/src/agent/prompt/

Comparative Analysis

1. Agent Architecture

Feature OpenCode Crush AmpCode
Multi-Model Support
Dynamic Model Switching
Agent Types Built-in + Custom Built-in + Custom Built-in + Custom
Real-time Events
Session Persistence

2. Agent Specialization & Capabilities

Feature OpenCode Crush AmpCode
Pre-built Specialist Agents ⚠️ Limited (build, plan, explore) ⚠️ Basic Advanced (Oracle, Librarian, Subagents)
Autonomous Subagent Spawning ❌ Limited ❌ Limited Full Support
Second-Opinion Reasoning ❌ No ❌ No Oracle System
Cross-Repository Search ❌ No ❌ No Librarian Agent
Agent Skills System ❌ No ⚠️ Basic (Agent Skills) Comprehensive
Workflow Orchestration ⚠️ Manual ⚠️ Manual Automated

3. Tool Integration

Feature OpenCode Crush AmpCode
MCP Support
Custom Tools
Toolbox System ❌ No ❌ No Advanced
Permission Granularity ✅ Advanced ✅ Good ✅ Advanced
Real-time Tool Execution

4. Context Management

Feature OpenCode Crush AmpCode
Context Window Size Standard Standard 200k tokens
Thread Sharing ❌ Limited ⚠️ Basic Full System
Handoff Between Sessions ❌ No ❌ No Supported
Context Compaction Intentionally Removed
Cross-Thread References ❌ No ❌ No Supported

5. Development Workflow Integration

Feature OpenCode Crush AmpCode
LSP Integration
IDE Extensions ✅ (VS Code, etc.) ⚠️ Terminal-focused ✅ (VS Code, JetBrains, etc.)
Build/Test Integration
Git Integration
Custom Commands ❌ Limited ⚠️ Basic Full System

6. Enterprise Features

Feature OpenCode Crush AmpCode
Team Collaboration ⚠️ Basic ❌ No Advanced
Thread Visibility Controls ❌ No ❌ No Granular
SSO Integration ❌ No Full Support
Cost Attribution ❌ No ❌ No Per-user tracking
Managed Settings ❌ No ❌ No Enterprise policies

Critical Gaps for OpenCode

1. Autonomous Agent Orchestration

Gap: OpenCode lacks autonomous subagent spawning and multi-agent workflows Impact: Limited ability to handle complex, parallelizable tasks Priority: HIGH

2. Specialized Agent Ecosystem

Gap: No equivalent to AmpCode's Oracle (reasoning) or Librarian (search) agents Impact: Missing high-value specialized capabilities Priority: HIGH

3. Context Management Innovation

Gap: No thread sharing, handoff, or cross-referencing Impact: Poor continuity between sessions and team collaboration Priority: HIGH

4. Workflow Automation

Gap: No custom commands, skills system, or automated workflows Impact: Requires more manual intervention Priority: MEDIUM

5. Enterprise Collaboration

Gap: No team features, thread sharing, or collaboration tools Impact: Limited for enterprise adoption Priority: MEDIUM

OpenCode Advantages

1. Permission System Sophistication

  • Strength: Most granular and flexible permission system
  • Advantage: Better security and control

2. Multi-Platform Support

  • Strength: Broader platform support (Windows, Linux, macOS)
  • Advantage: More accessible deployment options

3. Tool Ecosystem

  • Strength: Rich tool registry and MCP integration
  • Advantage: Extensible and customizable

Strategic Recommendations

Immediate (Q1 2025)

  1. Implement Subagent System

    • Add Task tool for spawning independent agents
    • Create agent coordination framework
    • Enable parallel task execution
  2. Add Specialized Agents

    • Oracle: Second-opinion reasoning agent
    • Librarian: Cross-repository search agent
    • Implement agent spawning logic

Short-term (Q2 2025)

  1. Context Management Overhaul

    • Thread sharing and collaboration
    • Handoff system between sessions
    • Cross-thread references
  2. Custom Commands & Skills

    • Command palette system
    • Skills package discovery
    • Reusable workflow automation

Medium-term (Q3-Q4 2025)

  1. Enterprise Features

    • Team workspaces
    • Thread visibility controls
    • Cost tracking and attribution
  2. Advanced Workflow Orchestration

    • Multi-step planning agents
    • Automated task breakdown
    • Progress tracking and recovery

Implementation Roadmap

Phase 1: Agent Foundation (6 weeks)

  • Extend agent.ts to support subagent spawning
  • Add Task tool implementation
  • Create agent coordination primitives

Phase 2: Specialist Agents (8 weeks)

  • Implement Oracle reasoning system
  • Build Librarian search agent
  • Add agent selection logic

Phase 3: Context & Collaboration (10 weeks)

  • Thread sharing infrastructure
  • Handoff system implementation
  • Cross-reference capabilities

Phase 4: Enterprise & Automation (12 weeks)

  • Team workspace features
  • Custom commands system
  • Skills package manager

Competitive Positioning

After implementing these features, OpenCode would:

  • Match AmpCode's core agent capabilities
  • Exceed both competitors in permission granularity
  • Lead in multi-platform support
  • Compete effectively in enterprise market

Success Metrics

  • User adoption of subagent features
  • Reduction in task completion time
  • Increased agent specialization usage
  • Team collaboration adoption
  • Enterprise feature utilization

This analysis identifies clear, actionable gaps while recognizing OpenCode's existing strengths. The roadmap provides concrete steps to achieve competitive parity and differentiation.