docs: add OpenCode server integration specification #94
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Detailed spec for integrating OpenCode server capabilities with agent relay: - OpenCodeWrapper class using HTTP API instead of PTY - WrapperFactory for automatic backend selection - Session forking for context inheritance between agents - mDNS discovery for multi-host coordination - Dashboard API extensions for OpenCode features The spec includes component interfaces, data flows, implementation phases, and testing strategy for seamless integration.
Expands the OpenCode integration spec with: - Cloud production architecture diagram - OpenCode as provider type with credential management - OpenCodeCloudWrapper for cloud-hosted instances - Cloud OpenCode Orchestrator design - CloudSyncService extensions for credential sync - Dashboard integration with provider settings - Cloud API specification with all endpoints - SSE event streaming from cloud - Updated implementation phases (5 phases) - Detailed open questions with recommendations The goal is seamless UX: user connects OpenCode provider, agents work automatically with no config changes needed.
- Add 6 detailed user flow diagrams with ASCII art: 1. First-time OpenCode setup (cloud) 2. Spawning an agent with OpenCode 3. Agent-to-agent communication 4. Session forking (context inheritance) 5. Local OpenCode server (no cloud) 6. BYOK (bring your own keys) setup - Fix authentication model confusion: - OpenCode Zen uses API key (not OAuth) - BYOK uses underlying provider OAuth (Anthropic/OpenAI) - Updated OpenCodeProvider code with connectWithZenApiKey() - Add authentication model summary table - Add spec review section documenting: - What the proposal does well - Issues identified and fixed - Remaining considerations - Architecture validation - Recommended implementation order
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Detailed spec for integrating OpenCode server capabilities with agent relay:
The spec includes component interfaces, data flows, implementation phases,
and testing strategy for seamless integration.