Opencode FAQs

Question 1

How does Opencode facilitate communication and discovery between instances?

Accepted Answer

It leverages SSH reverse tunnels. Each OpenCode instance connects via an SSH tunnel to a central relay, allowing the Opencode server to discover, health-check, and interact with these instances through localhost ports on the relay machine.

Question 2

What is the Model Context Protocol (MCP) API used for in Opencode?

Accepted Answer

The MCP API provides a standardized interface for interacting with and managing connected OpenCode instances. Through this API, users can perform actions like listing instances, creating and managing chat sessions, sending messages, and checking instance status.

Question 3

What is Opencode and what is its primary function?

Accepted Answer

Opencode is an MCP server designed to orchestrate, monitor, and drive multiple OpenCode instances. It enables their discovery and communication across various distributed machines, primarily using secure SSH reverse tunnels.

Question 4

How are OpenCode instances securely connected and managed?

Accepted Answer

Security is primarily handled by SSH reverse tunnels, which act as the authentication boundary. OpenCode instances bind their HTTP side-car to `127.0.0.1`, ensuring that their APIs are only accessible through the secure SSH tunnel, eliminating the need for additional passwords.

Question 5

Can Opencode integrate with other networking or deployment solutions?

Accepted Answer

Yes, Opencode features a pluggable transport layer, designed for future integrations with services like Tailscale or Cloudflare Tunnels. It can also be integrated into existing Docker-based deployments, such as `mcp-gateway`, using host networking and shared registry directories.

Opencode

Opencode

Key Features

Use Cases

Key Features

Use Cases