EPIC: Matrix/Element Bridge Integration #377

New Issue

jason.woltje · 2026-02-15T07:00:19Z

jason.woltje commented

2026-02-15 07:00:19 +00:00

Overview

Add Matrix protocol support as an alternative chat platform bridge alongside Discord. The existing IChatProvider interface (apps/api/src/bridge/interfaces/chat-provider.interface.ts) already abstracts platform-specific details — this epic adds a Matrix implementation.

Motivation

Replace Discord dependency (privacy concerns, ID verification requirements)
E2EE agent control via Element clients (mobile, desktop, web)
Federated protocol — no vendor lock-in
Matrix rooms provide natural workspace isolation
Element clients available on all platforms without app store dependency

Architecture

Matrix complements the existing communication stack:

Layer	Current	After Matrix
Internal real-time (PWA)	Socket.IO	Socket.IO (unchanged)
Job queue	BullMQ + Valkey	BullMQ + Valkey (unchanged)
Status broadcasting	Herald Service	Herald + Matrix output adapter
External control	Discord bridge	Discord + Matrix bridges (both via IChatProvider)
AI chat streaming	Unimplemented	Matrix message edits enable streaming

Key Integration Points

IChatProvider — Matrix service implements existing interface
CommandParser — Shared across all bridges (platform-agnostic)
Herald — Needs Matrix output adapter for status broadcasts
BridgeModule — Register MatrixService alongside DiscordService
Workspace → Matrix Room mapping (1:1)

Sub-Issues

See linked issues in this milestone for implementation breakdown.

## Overview Add Matrix protocol support as an alternative chat platform bridge alongside Discord. The existing `IChatProvider` interface (`apps/api/src/bridge/interfaces/chat-provider.interface.ts`) already abstracts platform-specific details — this epic adds a Matrix implementation. ## Motivation - Replace Discord dependency (privacy concerns, ID verification requirements) - E2EE agent control via Element clients (mobile, desktop, web) - Federated protocol — no vendor lock-in - Matrix rooms provide natural workspace isolation - Element clients available on all platforms without app store dependency ## Architecture Matrix **complements** the existing communication stack: | Layer | Current | After Matrix | |-------|---------|-------------| | Internal real-time (PWA) | Socket.IO | Socket.IO (unchanged) | | Job queue | BullMQ + Valkey | BullMQ + Valkey (unchanged) | | Status broadcasting | Herald Service | Herald + Matrix output adapter | | External control | Discord bridge | Discord + Matrix bridges (both via IChatProvider) | | AI chat streaming | Unimplemented | Matrix message edits enable streaming | ## Key Integration Points - `IChatProvider` — Matrix service implements existing interface - `CommandParser` — Shared across all bridges (platform-agnostic) - `Herald` — Needs Matrix output adapter for status broadcasts - `BridgeModule` — Register MatrixService alongside DiscordService - Workspace → Matrix Room mapping (1:1) ## Sub-Issues See linked issues in this milestone for implementation breakdown.

jason.woltje added the api api labels 2026-02-15 07:00:19 +00:00

jason.woltje referenced this issue

2026-02-15 07:00:33 +00:00

Install matrix-bot-sdk and create MatrixService skeleton #378

jason.woltje referenced this issue

2026-02-15 07:00:42 +00:00

Register MatrixService in BridgeModule with conditional loading #379

jason.woltje referenced this issue

2026-02-15 07:00:53 +00:00

Workspace-to-Matrix-Room mapping and provisioning #380

jason.woltje referenced this issue

2026-02-15 07:01:07 +00:00