muse-chief-relay is a public, MIT-licensed project for putting agents from different vendors and a human in one hack.chat room. It pairs a .NET 8 C# bridge, which keeps an agent connected and exchanges messages through files, with a Vue 3 browser client for chat, a read-only room board, and live watch. It is a relay and interface—not a new AI model—and its key safety advice is to trust verified tripcodes rather than display names.
What the project does
Project author Ismael Otero (who also identifies himself as Alex) describes muse-chief-relay as a way for “several agents from different vendors, plus a human, sharing one room.” The participants communicate through hack.chat; the project supplies the bridge and browser interface around that service. It does not itself provide the AI models.
As an Amazon Associate I earn from qualifying purchases.
The author’s stated reason for choosing hack.chat is that WSS over HTTPS on port 443 may work in environments where MQTT over TCP does not. That is a rationale for this design, not a guarantee that hack.chat or WSS will work on every network. The author’s original project article is on DEV Community, and the project is described at its GitHub repository.
How the bridge and client fit together
The .NET bridge
Chief.Bridge connects to hack.chat over WSS using .NET’s ClientWebSocket. It reads configuration from config.json, appends inbound frames to inbox.jsonl, watches outbox.jsonl for outbound lines, and writes connection information to state.json. This file-based inbox/outbox design gives an agent or local process a simple way to consume incoming messages and submit replies.
#1 Best Overall
The author describes retry and reconnection handling for issues including DNS failures, refused connections, TLS problems, stalled handshakes, join warnings, and missed onlineSet events. Retries are an implementation feature, not a measured uptime or uninterrupted-service guarantee. The article also describes a watch mode and a webhook poller that can wake an agent.
The Vue client
The browser application is described as Vue 3, Vite, and Tailwind. It offers three views:
- Chat: send ordinary chat messages or protocol JSON.
- Board: a read-only view backed by a channel-hash JSONL file.
- Live watch: watch activity in the room.
The project’s protocol documentation, identified as docs/protocol.md, describes task, opinion, result, and acknowledgement message forms. Those labels suggest a lightweight way to coordinate work, but they do not by themselves establish that agents share a standardized protocol across vendors. The static browser build is described as residing under docs/muse.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Identity is the central safety concern
hack.chat nicknames are first-come, first-served. A participant can therefore use a name that looks like a trusted agent or person. The author’s memorable rule is “trust the trip, not the nick”: check the sender’s tripcode on every message that could trigger an action, rather than treating a familiar display name as proof of identity.
For the public status view, the described publishing controls require both a repository listed in publish_repos and a message tripcode listed in publish_trips. An empty trip allowlist publishes nothing. The author also describes filtering webhook wake-ups and optional automatic acknowledgements by trusted trips. These checks are useful safeguards, but they should not be mistaken for a complete security guarantee. See the project’s security documentation for its stated trust model.
- Use a channel you control, and treat its name as a weak secret: anyone who learns it may be able to read the room.
- Do not put passwords, access tokens, or personal data in chat payloads.
- Keep a person responsible for consequential actions such as merges, deployments, public posts, and spending.
- Shared knowledge notes are public by design; the author says the knowledge checker fails closed on private notes or obvious secrets.
As Otero puts it: “The lesson I keep relearning: on a shared chat transport, identity is not the display name. Design for impostors first, then add convenience.” This is the project author’s guidance, not an independently validated security standard.
Rank #4
Setup requirements and basic run paths
The project article specifies .NET 8 for the bridge and Node 20 or later for the browser client. Those are the versions named in that article; it does not establish the current release requirements, so check the repository before installing.
Run the bridge
- Copy
config.example.jsontoconfig.json. - Set the channel and nickname; configure
baseandpassif needed for your use. - Run the Chief.Bridge project, or install the packaged .NET global tool as described by the project.
Run the browser client
- From
web/muse, install dependencies withnpm install. - Start the development server with
npm run dev. - Alternatively, serve the committed static build under
docs/muse.
These commands and paths reflect the setup article; repository contents, dependency versions, and hosted-page availability may have changed. The project pages are at signalnotnoise.github.io/muse-chief-relay.
What the project establishes—and what it does not
muse-chief-relay offers a concrete design for sharing a chat room across agents and a human: a WSS-connected bridge, a file-based message workflow, and a Vue interface with chat, board, and live-watch views. Its distinctive design constraint is not model capability but coordination and identity: a shared room is easy to understand, while display names alone are unsafe as authentication.
The author’s article does not provide comparative tests of hack.chat against other transports or room products, nor does it establish current service behavior, availability, or policies. Treat its implementation details as the author’s description, and assess network access, persistence, authorization, and operational needs for your own environment before relying on the room for work.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
