headquarter/openspec/changes/opencode-web-terminal/proposal.md at fba01ddfb29aad8cc7204bd47255b392f073467b

Files

T

Fusion ac6bd3304d feat(opencode-web-terminal): complete OpenCode web terminal implementation

- Update OpenCode compose template with web server on port 3000
- Add default_port=3000 and interfaces=[terminal, web] to OpenCode seed data
- Remove hardcoded 8080 fallback in tunnel creation
- Fail gracefully when tool type has no default_port configured
- Update frontend ToolType API to include default_port, category, interfaces
- Add port, category, and interfaces fields to tool type creation form
- Display port and interfaces in tool type cards
- Create migration 0012 to make default_port non-nullable
- Set default_port values for existing built-in tool types
- Quality gates: typecheck ✓, build ✓, Python syntax ✓

2026-05-20 17:17:50 +02:00

1.7 KiB

Raw Blame History

Why

Tool instances currently have inconsistent port configuration. OpenCode lacks a default port and doesn't expose a web interface, while code-server and jupyter have hardcoded ports. We need a systematic way to define tool ports and ensure OpenCode works properly via the web terminal interface.

What Changes

Tool Port Configuration: Make default_port required for all tool types and validate it during tool type creation
OpenCode Web Terminal: Configure OpenCode to run a web server (e.g., on port 3000) so it can be accessed via browser, not just through the raw WebSocket terminal
Tunnel Port Discovery: Ensure cloudflared tunnels use the correct internal port from the tool type definition
Terminal-First Tools: Add support for tools that primarily use the terminal interface but may also expose a web UI
Tool Validation: Add validation to ensure tool compose templates expose the port defined in default_port

Capabilities

New Capabilities

tool-port-configuration: Systematic port definition and validation for tool types
opencode-web-server: Running OpenCode with a web interface accessible via browser

Modified Capabilities

tool-types: Adding port validation requirements and web interface support for terminal tools
tool-instances: Tunnel creation must read port from tool type configuration
tool-terminal: Terminal tools may optionally expose web endpoints

Impact

Backend: Tool type model, validation, seed data, tunnel creation logic
Frontend: Instance list may show both Open (web) and Terminal buttons for tools with dual interfaces
Docker: OpenCode compose template needs a web server command
Infrastructure: Cloudflared tunnels must target the correct internal port

1.7 KiB Raw Blame History

Why