- Replace three-step work preference dials with 0-100 score scale (desktop schema, prompts, frontend form, presets, styles, locales) - Restructure general settings panel layout with WorkPreferences section - Update landing page copy and README download details - Update related frontend and desktop tests Checks: npm --prefix frontend test (369 passed), node --test desktop/test/workspace/work-preferences.test.cjs (3 passed)
English · 简体中文
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.
Download Meldwork V1.0.6 for Apple silicon macOS · Architecture · License
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
- Select the Agents that will work on the task together.
- Scope the goal, working directory, context, attachments, Skills, knowledge sources, and permissions.
- Collaborate in Auto Discussion: let Agents discuss approaches, carry out authorized work, and check results. Direct conversations and Concurrent Responses are also available.
- Decide when the work needs information, permission, or a tradeoff resolved.
- Check the result and request changes when more work is needed.
Collaboration modes
| Mode | What happens | Best for |
|---|---|---|
| Direct | One selected Agent keeps its conversation and native session when supported. | Focused research, writing, analysis, or execution. |
| Concurrent Responses | Selected Agents receive the same frozen task snapshot and return independent responses in stable order. | Comparing perspectives before choosing a path. |
| Auto Discussion V4 | Agents propose independently, discuss, request peer contributions, carry out authorized work, and check deliverables. A delivery owner judges progress and requests user decisions when needed. Native sessions continue when supported. | Multi-step collaboration with less manual coordination. |
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:
Codex |
Hermes |
OpenClaw |
WorkBuddy |
Pi Agent |
Kimi Code |
MiMo Code |
Claude Code |
Gemini CLI |
OpenCode |
Qwen Code |
OpenCodeReview |
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.6
For Apple silicon macOS, download the Meldwork V1.0.6 prerelease and choose Meldwork-0.1.6-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.6
V1.0.6 improves long-lived Agent recovery, keeps group discussions going through individual failures, and lets conversations run independently even in the same folder. It delivers attachments and knowledge sources to group Agents, restores WorkBuddy's bundled CLI launch, and tightens ACP and WorkBuddy permission checks.
The interface starts without waiting for Agent detection, highlights conversations awaiting your decision, explains why an installed Agent is unavailable, and adds General settings with System, Light, and Dark appearance options.
Release verification includes 357/357 frontend tests, 1,603/1,603 desktop tests, six deterministic evaluation cases with 18 results, web and desktop builds, packaging, DMG checksum and ZIP integrity checks, and code-signature verification. The packaged Apple silicon app launched with a fresh profile without main-process faults. Real Agent group execution, cancellation, and restart acceptance were not repeated for this release. The artifacts remain ad-hoc signed and unnotarized; live behavior still depends on the installed Agent CLI version, authentication, Provider, and capabilities.
Documentation
License
Meldwork is source-available under the Meldwork Non-Commercial Source License 1.0. You may inspect, run, modify, and share it for non-commercial purposes. Commercial use requires prior written permission; see COMMERCIAL_USE.md.
