One feed in your browser.
RelayDesk is now being built as a web-only unified communication app. Matrix is the first bridge/transport adapter, but the app is designed so Matrix, direct provider APIs and future transports can all plug into the same RelayDesk feed.
Quick start
Open the app
Go to /rd1-app/. RelayDesk starts in All Feeds mode, combining clearly-labelled demo providers, the local Test Lab identity and any connected live Matrix events into one timeline.
Connect Matrix
Open Connectors and enter the HTTPS address of a test Matrix homeserver plus a test-account access token. Web 2.2.0 keeps that test configuration only in browser session storage. Matrix is also the first transport path for the WhatsApp Bridge Mode experiment; a real WhatsApp bridge must actually be installed and paired before private WhatsApp traffic can appear.
Sync and reply
Use the Matrix configuration panel to test the transport boundary and session handling. Web 2.2.1 keeps Matrix in developer-preview mode: test configuration can be exercised in the client, but production authentication and durable server-side connector sessions still need to be completed before RelayDesk should be trusted with high-value accounts.
Universal Inbox
Web 2.2.1 starts in Threads mode. Outlook, Gmail, WhatsApp, Teams, the active RelayDesk Test Lab identity and Matrix developer-preview traffic first land in the same canonical queue, then RelayDesk groups visible events around the person/thread when it has enough identity information. Provider names remain visible inside the thread. Use Events when you want every individual message instead of the grouped person view. The source strip and Action Needed controls still let you isolate a provider or actionable work without leaving the combined feed.
WhatsApp Bridge Mode
Bridge Mode is the Web 2.2.0 default. RelayDesk does not preload or keep WhatsApp Web resident. In Connect, choose Bridge Setup: connect Matrix, then pair WhatsApp through an installed bridge as a linked device using its QR-code or phone-pairing flow. Once the bridge is genuinely available, WhatsApp conversations can be normalized into the same Unified Feed. Open Native Temporarily is a fallback for provider-native features; close that separate tab when finished. Web 2.2.0 does not claim a real WhatsApp bridge is already deployed.
Unified Threads
Web 2.2.1 makes Unified Person Threads the default feed experience. When the same current-preview person appears in Outlook and Teams, RelayDesk collapses those feed events into one person/thread card and opens their combined chronological history in the conversation pane while keeping each provider, account and timestamp visible. Use the Events toggle to inspect every underlying message. Test Lab contacts use stable local peer IDs. Production identity resolution must use provider identifiers and explicit user-controlled contact links, with a way to split an incorrect merge.
Return Path Router
Web 2.2.2 separates the human thread from the outbound route. A single person thread can contain Outlook, Teams, WhatsApp, Matrix or other events, but the selected event keeps its provider and account as the default return path. The conversation pane now shows Reply via provider · account before Send. Local Test Lab replies use a working browser-local route. Demo/provider items use a clearly-labelled Route Test that records the outbound intent locally without sending external data until a real connector supports outbound send.
Holistic Services Hub
Turn a message into work without caring which provider delivered it.
Create a calendar/service intent from the same conversation context.
Capture person/contact intent above provider-specific address books.
Prepare a service/AI intent without automatically sending private data to an AI provider.
These service actions are local preview intents in Web 2.2.2. Production execution will require approved calendar, task, CRM, contacts or AI adapters.
Attention workflow
Shows unread, high-priority or explicitly Follow-Up conversations that are not snoozed.
Pin keeps important conversations at the top. Save creates a durable personal collection.
Follow Up keeps a conversation actionable. Snooze hides it from normal views for one hour in this preview.
Web 2.2.0 stores this attention state locally in the browser so the workflow behaves consistently across Demo, Test and Live Matrix items. Provider-side read/snooze synchronization is connector-dependent and is not implied by the preview.
RelayDesk Core Foundation
Web 2.2.0 adds a portable RelayDesk Core state envelope. In Connectors, use Export Core State to download Test Lab messages, the active test identity, attention state and basic UI preferences. The Matrix access token is deliberately excluded. This is the migration bridge from browser-local testing to a future authenticated RelayDesk backend.
What Matrix does
Matrix gives RelayDesk one standards-based way to consume Matrix rooms. Separate Matrix bridge services can connect some third-party systems into those rooms. That can dramatically broaden coverage, but the bridge must actually exist, be configured, and have legitimate access to the target network.
Working Web 2.2.0 application preview: connect, sync, normalize, deduplicate, group by conversation, open a conversation workspace, monitor connector health, detect browser online/offline state and send Matrix text messages.
Potential route for networks such as Slack, Telegram, WhatsApp, Discord, Signal, SMS and others where a suitable bridge is deployed.
Microsoft Graph, Slack API, Gmail and other direct integrations can bypass Matrix and still land in the same feed.
What “pluggable” means
Matrix adapter ---------\ Microsoft adapter -------+--> RelayDesk canonical feed --> search / filters / actions Slack adapter -----------+ Email adapter ----------/
RelayDesk owns the neutral message model and user experience. Replacing Matrix, adding another bridge or adding a direct connector should not require redesigning the feed.
What “Matrix as backend” means
Matrix can be the communication hub: rooms, homeserver sync and reviewed bridges can carry messages from many networks. RelayDesk still needs its own application core for user accounts, connector settings, priorities, rules, automation and future AI permissions. Keeping those layers separate makes the system easier to replace, secure and scale.
Important privacy note
The current Matrix connector is a developer preview. Use a test Matrix account rather than a high-value production account. Production RelayDesk authentication should use a stronger server-side/session design and should not leave long-lived provider credentials in browser storage.
Use the 2.3.0 Action Center
Open a message and choose Create Task, Schedule, Save Contact or Summarize. The item is stored locally and appears under Actions.
Use Actions to complete tasks, promote message follow-ups, export calendar events, copy drafts and review saved contacts.
Open Workspace to import JSON, CSV or EML files into the Unified Feed. Imported items remain on this device.
Export a RelayDesk backup before clearing browser data or moving devices. Connector passwords and temporary access tokens are excluded.
Local summaries use simple on-device text rules in this preview; they are not sent to an Artificial Intelligence provider. Production account sync and external provider send remain future connector/backend work.