Ryder Sun
e1500a73ef
Sending to an Agent while the same Agent (or any Agent) was busy in another conversation made the new conversation sit on 'Running' until the first one finished. The cause was the writer lease, which was keyed by the real folder: every writable conversation that used the same folder (and most keep the default one) took turns, one at a time, across groups and direct chats.9198bf6had deliberately scoped the lease of direct chats to the chat so that one writable chat could not block another Agent.17cbd32reverted that as a regression and added a 'waiting for another Agent writing in the same folder' notice. That was the wrong call: it made the product behave like a single queue. This commit reverts17cbd32and goes one step further than9198bf6: - the writer lease is scoped to the conversation for groups as well as direct chats, so conversations never wait for each other; writers inside one conversation still take turns - the waiting notice, the waitingForWorkspaceKinds snapshot field and the scheduler queue callbacks that only existed for the folder lock are removed with the revert - the old rule 'group chats serialize writes across symlink aliases' is replaced by its opposite; new tests cover the same Agent in two direct chats and a group at once, group chats sharing a folder through a symlink alias, and that turns of one conversation share a lease scope while another conversation in the same folder does not - architecture.md states the new rule and the trade-off Trade-off: two Agents in different conversations can now edit the same files at the same time, like two terminals in one directory. Output capture compares .meldwork-output/ before and after a run, so when two conversations produce deliverables in the same folder at the same time one may attach a file the other wrote. No guard was added for that. The new write-scheduling tests fail on the previous commit (two fail, one never gets its second Agent started). Checked with: local-workspace-write-scheduling (6 pass), run-scheduler, run-coordinator, state, harness, npm --prefix frontend test (333 pass).
English · 简体中文
Meldwork — A local-first workspace for General Agents
Turn several General Agents into a reviewable working group. Meldwork gives every task a shared context, lets selected Agents investigate independently or discuss across rounds, and keeps the evidence and human decision visible before anything is adopted.
Meldwork is a local-first Electron workspace for using the Agent tools you already have on your Mac. It supports focused conversations, independent concurrent responses, and Auto Discussion V4 for proposal, challenge, negotiated work, synthesis, and verification. Agents can work with text, files, images, media, Skills, and selected knowledge sources, so the same workspace can support research, analysis, writing, planning, review, and implementation.
The product is organized around a durable review record: Case → Finding → Evidence → Decision → Disposition. Meldwork keeps the task snapshot, Agent contributions, run state, artifacts, Human Gates, and adoption decision together in one local work cell. Workspace writes are opt-in and remain under the user's control.
Download Meldwork V1.0.5 for Apple silicon macOS · Architecture · License
What Meldwork is for
Meldwork is useful when a decision benefits from more than one perspective and a clear record of why a result was adopted. 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 and review tasks where findings, evidence, permissions, and the final adoption decision should remain inspectable.
How a task moves through Meldwork
- Select the Agents and participants for this Case.
- Scope the goal, working directory, context, attachments, Skills, knowledge sources, and permissions.
- Run a direct conversation, Concurrent Responses, or Auto Discussion V4.
- Review the findings, evidence, artifacts, trace, and any Human Gate.
- Adopt the approved result or leave the Case unresolved for further work.
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, challenge, negotiate responsibilities, execute agreed work, synthesize a candidate result, and verify it across bounded rounds. Native Agent sessions continue when supported. | Multi-step work that needs discussion, division of responsibility, and review. |
Participants are selected by the user. Automatic selection from a larger roster is outside the current preview.
The review record
Meldwork treats collaboration as a decision process rather than a stream of chat messages:
- Case defines the question, scope, context, and permissions.
- Finding records an Agent's claim, observation, or proposed action.
- Evidence links the finding to a response, artifact, file, knowledge result, or other bounded reference.
- Decision records what the evidence supports, what remains uncertain, and which path is selected.
- Disposition records whether the result was accepted, revised, rejected, superseded, or left unresolved.
The Run Ledger preserves phase, participant, attempt, receipt, artifact, recovery, and Human Gate state. Diagnostic tool output and sensitive runtime details stay behind the Electron main-process boundary.
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.5
For Apple silicon macOS, download the Meldwork V1.0.5 prerelease and choose Meldwork-0.1.5-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.5
V1.0.5 improves local Agent readiness and recovery, preserves healthy participants when another Agent fails, keeps completed and stopped work visible after restart, and tightens group execution and output handling. It also updates the workspace preference flow, sidebar and titlebar details, and the Pi capability probe contract.
Verification for this prerelease includes 343/343 frontend tests, 1,562/1,562 desktop tests, six deterministic evaluation cases with 18 results, web and desktop builds, packaging, ZIP integrity, deep code-signature verification, and packaged macOS acceptance for group execution, cancellation, and restart recovery. 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.