Meldwork — Let Agents collaborate to move tasks forward

Set the goal. Let Agents work together. Meldwork brings your existing Agents into one working group to share context, discuss approaches, carry out work, and check each other's results — with less relaying, prompting, and stitching outputs together.

Meldwork is a local-first multi-Agent collaboration workspace for the Agent tools you already use on your Mac. Once you choose the participants, goal, context, and permissions, Agents in Auto Discussion can build on each other's work, request contributions or reviews, and advance the task within the authorized scope. Direct conversations and independent concurrent responses also support research, analysis, writing, planning, review, and implementation.

You do not need to direct every round, but you still set the goal, grant permissions, and make key decisions. Missing information, permission requests, or tradeoffs may require your input. Workspace writes are opt-in; collaboration history, run state, and deliverables stay local so you can revisit the work and continue it.

What Meldwork is for

Meldwork is useful when several Agents need to advance the same task and you want to spend less time passing context and coordinating next steps. Typical work includes:

• research and information synthesis across local Agent tools and selected knowledge sources;
• product, market, operational, and technical analysis;
• writing, planning, review, and structured document work;
• multimodal work with local documents, images, audio, video, PDFs, and code or configuration files;
• implementation in an authorized workspace, with other Agents checking the deliverables and requesting revisions.

How a task moves through Meldwork

1. Select the Agents that will work on the task together.
2. Scope the goal, working directory, context, attachments, Skills, knowledge sources, and permissions.
3. Collaborate in Auto Discussion: let Agents discuss approaches, carry out authorized work, and check results. Direct conversations and Concurrent Responses are also available.
4. Decide when the work needs information, permission, or a tradeoff resolved.
5. Check the result and request changes when more work is needed.

Collaboration modes

Participants are selected by the user. Automatic selection from a larger roster is outside the current preview.

Revisit the process and continue the work

Meldwork keeps task context, Agent replies, run state, and deliverables locally so you can see how work progressed, where it stalled, and what needs attention next. The Run Ledger preserves phase, participant, attempt, artifact, recovery, and Human Gate state. Diagnostic tool output and sensitive runtime details stay behind the Electron main-process boundary.

These records help you inspect collaboration; they do not establish that every claim has been fact-checked. Peer review does not guarantee correctness, and important deliverables still need acceptance checks appropriate to their use.

General Agent catalog

Meldwork detects and invokes compatible locally installed Agent commands. The catalog currently includes:

Approved Agent Connectors and custom executable Agents use the desktop connector paths. The desktop guide contains the current adapter, installation, provider, and capability matrix.

Context and local boundaries

Meldwork runs as a local Electron application. Conversations, group configuration, run records, and app-owned attachments stay in the local user data directory. The renderer receives only validated snapshots through a narrow preload API; executable paths, credentials, native session references, Skill paths, and unrestricted shell access remain in the main process.

Selected Agents may send prompts, attachments, or Skills to the model provider configured in their own CLI. Knowledge access is explicit and bounded: the current implementation supports local Obsidian retrieval and CLI-owned Feishu or DingTalk access modes. Local-first describes where Meldwork stores and coordinates work; it does not promise that an Agent's model provider is offline.

Download V1.0.9

For Apple silicon macOS, download the Meldwork V1.0.9 prerelease and choose Meldwork-1.0.9-arm64.dmg. The release also includes a ZIP archive and SHA-256 manifest. Install at least one supported local Agent CLI before opening the app.

The preview artifacts are ad-hoc signed and not notarized with an Apple Developer ID. macOS may require Open Anyway under System Settings → Privacy & Security on first launch.

Run from source

Prerequisites: Node.js 22.12+ and npm.

npm --prefix frontend ci
npm --prefix desktop ci
npm --prefix desktop run dev

Before distributing a build:

npm --prefix frontend test
npm --prefix frontend run build
npm --prefix frontend run build:desktop
npm --prefix desktop test

V1.0.9

Auto Discussion can complete native Agent turns on explicit completion and requires each participant to approve the same delivery version. A real six-Agent unlimited discussion completed in nine rounds with matching delivery hashes. This preview also improves Agent authentication status, handles CLI authentication errors reported on stderr, and bundles knowledge-base logos.

Agent installation does not guarantee a working model connection: OpenClaw's isolated runtime may not support the native environment configuration, WorkBuddy's CLI may require its own login, and Zcode needs valid native provider credentials. Desktop and frontend regression checks passed 1,700 and 379 tests respectively.

V1.0.8

V1.0.8 keeps Kimi read-only queries in manual approval mode instead of forcing a planning cycle, preserves MiMo's final text chunks, forwards supported native CLI configuration, and retains the selected Auto Discussion mode after sending. Repetitive native output is cancelled with partial replies preserved. Zcode remains before Pi Agent with its official logo and native default configuration; WorkBuddy can reuse a configured desktop model selected in Meldwork.

Real CLI acceptance covered all 13 installed Agents. A five-Agent unlimited discussion completed all 14 native calls through an isolated Magpie hotfix. The installed Magpie version can rewrite stop into tool_calls when tool_calls is null, causing OpenCode, MiMo, and Hermes to