opencode-bridge

Overview

OpenWork communicates with OpenCode via three mechanisms:

1. CLI invocation: Spawn opencode with prompts and get JSON responses.
2. Database access: Read OpenCode's SQLite database for sessions and messages.
3. MCP bridge: Real-time bidirectional communication for streaming and permissions.

CLI Invocation

Non-interactive mode

opencode -p "your prompt" -f json -q

Returns JSON with the response content.

Flags

Example response

{
  "content": "Here is the result...",
  "session_id": "abc123"
}

Database Access

Location

~/.opencode/opencode.db

Or project-local:

.opencode/opencode.db

Schema (key tables)

sessions

CREATE TABLE sessions (
  id TEXT PRIMARY KEY,
  parent_session_id TEXT,
  title TEXT,
  message_count INTEGER,
  prompt_tokens INTEGER,
  completion_tokens INTEGER,
  summary_message_id TEXT,
  cost REAL,
  created_at INTEGER,
  updated_at INTEGER
);