<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: earayu</title>
    <description>The latest articles on DEV Community by earayu (@earayu).</description>
    <link>https://dev.to/earayu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257610%2Fc248dd0a-e896-4911-988f-11cb54a52aed.jpg</url>
      <title>DEV Community: earayu</title>
      <link>https://dev.to/earayu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/earayu"/>
    <language>en</language>
    <item>
      <title>Mingle (MIT): Bring Your Local Coding Agents into Slack, Discord, Telegram &amp; More — With Zero Servers</title>
      <dc:creator>earayu</dc:creator>
      <pubDate>Sat, 21 Nov 2026 16:09:02 +0000</pubDate>
      <link>https://dev.to/earayu/mingle-mit-bring-your-local-coding-agents-into-slack-discord-telegram-more-with-zero-3cm4</link>
      <guid>https://dev.to/earayu/mingle-mit-bring-your-local-coding-agents-into-slack-discord-telegram-more-with-zero-3cm4</guid>
      <description>&lt;p&gt;Bringing your own coding agent (Claude Code, Codex, Cursor, OpenCode, Kimi Code, etc.) into custom tooling is pretty common now. What still bothered me about most agent-to-IM bridges was the &lt;strong&gt;cloud relay&lt;/strong&gt;: if a third-party server sits between your chat apps and your agent, your private work conversations pass through someone else's infrastructure—bringing both the risk of a server breach and the risk of your data being logged or sold.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="https://github.com/earayu/Mingle" rel="noopener noreferrer"&gt;&lt;strong&gt;Mingle&lt;/strong&gt;&lt;/a&gt; (MIT-licensed)—a &lt;strong&gt;zero-server desktop app&lt;/strong&gt; that lets you bring your local coding agents directly into the chat apps you already use: &lt;strong&gt;Slack, Discord, Telegram, iMessage, WeChat, Feishu/Lark, WeCom, DingTalk, QQ, and GitHub Issues/PRs&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcpfecdxsbm1yb1w47bl3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcpfecdxsbm1yb1w47bl3.png" alt="Mingle console showing one agent connected across multiple chat apps with parallel tasks" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why zero-server matters
&lt;/h2&gt;

&lt;p&gt;Mingle has &lt;strong&gt;no backend service at all&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;No Mingle server, no accounts, no telemetry.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Direct platform connections&lt;/strong&gt;: connects straight to each chat platform's official bot interface (or your local Apple ID for iMessage)—never routed through a hosted Mingle relay.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Localhost-only surface&lt;/strong&gt;: the local console and API bind to &lt;code&gt;127.0.0.1&lt;/code&gt; only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OS keychain for secrets&lt;/strong&gt;: bot tokens and credentials stay inside macOS Keychain, Windows DPAPI, or Linux Secret Service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Plain-file memory&lt;/strong&gt;: each agent's persona and memory are ordinary files in a local folder (&lt;code&gt;ROLE.md&lt;/code&gt;, &lt;code&gt;MEMORY.md&lt;/code&gt;, and &lt;code&gt;notes/&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Optional 24/7 mode on your own hardware&lt;/strong&gt;: if you want your agent online when your laptop sleeps, you can deploy the runtime to your own SSH host directly from the app—still your machine, no middleman.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What makes it usable in real chats
&lt;/h2&gt;

&lt;p&gt;Connecting a CLI agent to a webhook is easy to demo; making it behave well in daily group chats took most of the real engineering:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;One agent, unified memory across chat apps&lt;/strong&gt;
The same agent can join your Slack workspace, Discord server, and Telegram/WeChat groups while sharing one continuous memory. You can ask it in one app what was decided in another, or ask it to forward a summary across platforms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Parallel side tasks without blocking chat&lt;/strong&gt;
When you hand it heavy work—writing code, investigating a bug, running long shell commands—it forks the work into a background task (opening native threads in Slack, Discord, and Feishu) while staying responsive in the main room.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Group-chat etiquette&lt;/strong&gt;
It listens passively, responds when addressed by name or nickname without needing an &lt;code&gt;@&lt;/code&gt; on every message, and automatically throttles itself in busy channels instead of spamming every turn.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;14 coding-agent harnesses + one-click session handoff&lt;/strong&gt;
Supports Claude Code, Codex, OpenCode, Kimi Code, Cursor, and 9 more harnesses via OAR. You can also hand off an existing session's context and preferences into a Mingle agent in one click.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4pf89qqyyifl68g4uy20.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F4pf89qqyyifl68g4uy20.png" alt="Connecting a chat platform in Mingle" width="800" height="512"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Honest current status
&lt;/h2&gt;

&lt;p&gt;Mingle started about a week ago and is currently at &lt;code&gt;v0.4.8&lt;/code&gt;—definitely early:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;End-to-end verified harnesses&lt;/strong&gt;: Claude Code, Codex, OpenCode, and Kimi Code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Chat platforms&lt;/strong&gt;: Feishu is battle-tested on a live tenant; the other connectors are currently verified against platform APIs and automated tests.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Installers&lt;/strong&gt;: macOS (Apple-signed &amp;amp; notarized), Windows (unsigned for now), Linux, plus a one-line install script.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;GitHub (MIT)&lt;/strong&gt;: &lt;a href="https://github.com/earayu/Mingle" rel="noopener noreferrer"&gt;https://github.com/earayu/Mingle&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Website &amp;amp; docs&lt;/strong&gt;: &lt;a href="https://mingle.build" rel="noopener noreferrer"&gt;https://mingle.build&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you try it out, I'd love feedback on the zero-server architecture, the SSH deployment flow, or any quirks you hit with a specific chat platform—feel free to drop a comment here or open an issue on GitHub.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>osdc</category>
      <category>ai</category>
      <category>news</category>
    </item>
  </channel>
</rss>
