Comms Nexus

notion image
🛰️
Comms Nexus is a private, local command centre that brings Nasri’s conversations from multiple chat networks into one focused workspace, without bulk-syncing messages into the cloud.

What Comms Nexus is

Comms Nexus is a custom front end built on top of the Beeper Desktop API. Beeper already brings networks such as WhatsApp, Telegram, Signal, Instagram DMs, Messenger, Discord, and Slack into one inbox. Comms Nexus takes that unified data and turns it into a personal, local-first mission control for reading, triaging, and replying to conversations.
The product decision was intentionally simple: this is not an AI assistant that sends messages for you, and it is not a Notion archive of every chat. It is one screen that Nasri controls, where conversations stay central and sending remains manual.

Why it exists

The project began while troubleshooting an official Beeper MCP extension that would not connect. The real issue was not the extension, but a disabled Beeper Desktop API setting. Once the local API was working, the bigger opportunity became clear: build a practical command centre on top of it.
A full Notion sync was deliberately ruled out. High-volume chat data would create noise and duplicate maintenance, while Beeper’s API is local-only and can only be reached when the desktop app is running. The right model is therefore on-demand and local, with the option to save selected threads to Notion later.

How it works

Comms Nexus runs entirely on Nasri’s own machine:
  • A small Node and Express server securely holds the Beeper access token.
  • The server uses the @beeper/desktop-api SDK to fetch chats, messages, media, read state, and sending actions from localhost:23373.
  • A single-file HTML, CSS, and JavaScript dashboard provides the interface.
  • The app opens in Sample Mode if credentials are unavailable, then switches to LIVE when it can connect to Beeper.
  • Thin endpoints handle bootstrapping chats, loading history and media, uploading attachments, sending messages, and marking conversations read.

The experience

The interface was designed as a cyberpunk operations console: blue-black panels, neon cyan and magenta accents, subtle HUD details, and a three-zone layout.
  • Left: contacts and conversations.
  • Centre: the active conversation and manual reply composer.
  • Right: command rail with unread counts and network status.
It prioritises familiar messaging behaviour, including pinned chats first, then recent activity, real contact avatars and previews, opening a chat to mark it read, and support for text, images, videos, drag-and-drop, and paste-to-send attachments.

What the build taught

The build was as much about learning the API as writing the software. Key lessons included reading actual errors before assuming a feature was broken, handling message bodies returned as HTML, proxying encrypted mxc:// media through Beeper’s dedicated asset endpoint, and checking the exact token an app is using before diagnosing permissions.
One of the most useful fixes came down to a single field name: the API accepts a singular attachment object, not an attachments array. Testing safely in Telegram Saved Messages confirmed that image sending worked end to end.

Where it stands

Comms Nexus is a working local prototype built around privacy, control, and a calmer communication workflow. Planned improvements include older-history loading, image captions, optional per-channel saving to Notion, and a keyword digest across networks, all kept manual and local by default.
In one line: Comms Nexus is not about collecting every message. It is about giving scattered conversations one private place to be seen, handled, and replied to with intention.