From bb55fad0080fbbbf5bce2711b812c3aff68a0977 Mon Sep 17 00:00:00 2001
From: Ryder Sun
Download Meldwork V1.0.5 for Apple silicon macOS @@ -28,70 +20,49 @@ Unlike terminal multiplexers (tmux, zellij) that show raw output side by side, M · License
-## Who it is for +## What Meldwork is for -Use Meldwork when you: +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: -- run multiple AI coding agents (Codex, Claude Code, Gemini CLI, Hermes, OpenCode, etc.) and want to coordinate them without manually passing context between terminals; -- need independent review for code, research, or product analysis before choosing a path; -- want to compare multiple agents' responses to the same task side by side, with evidence trails and a human approval gate before any workspace writes; -- need inspectable traces, evidence, and human review for multi-agent coding sessions — so you can resume, audit, and reuse work across sessions. +- 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. -## Workflow +## How a task moves through Meldwork -1. **Select** the local Agents and participants. -2. **Scope** the goal, working directory, context, and permissions. -3. **Run** Direct, Concurrent Responses, or Auto Discussion V4. -4. **Review and adopt** the result, evidence, and any Human Gate before changing the workspace. +1. **Select** the Agents and participants for this Case. +2. **Scope** the goal, working directory, context, attachments, Skills, knowledge sources, and permissions. +3. **Run** a direct conversation, Concurrent Responses, or Auto Discussion V4. +4. **Review** the findings, evidence, artifacts, trace, and any Human Gate. +5. **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 work with one Agent. | -| **Concurrent Responses** | Selected Agents receive the same frozen task snapshot and return independent replies in stable order. | Comparing approaches before choosing one. | -| **Auto Discussion V4** | The first round runs concurrent proposals. Later turns follow the discussion: one Agent can route the next turn with `@Agent`, or several Agents can be selected for a concurrent response. Native Agent sessions continue across rounds. | Multi-round work that benefits from discussion, flexible routing, and review. | +| **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 always selected by the user. Automatic selection from a larger roster is outside the current preview. +Participants are selected by the user. Automatic selection from a larger roster is outside the current preview. -## How Meldwork differs +## The review record -Meldwork is a local-first multi-agent orchestration desktop app — not a terminal multiplexer, cloud agent fleet, communication network, or programmable orchestration framework. It connects the local Agent CLIs you already use to a decision-ready review workflow and keeps independent findings, evidence, responsibility, and the human adoption decision visible in one local workspace. +Meldwork treats collaboration as a decision process rather than a stream of chat messages: -If you're comparing Meldwork to other multi-agent orchestration tools, here's where it fits: +- **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. -| Tool | What it does | What Meldwork adds | -| --- | --- | --- | -| tmux / zellij | Terminal multiplexer — run agents in panes, manually copy context between them | Frozen task snapshots, evidence trails, human adoption gate, no manual context passing | -| Claude Code Agent Teams | Native subagent spawning within Claude Code only | Cross-CLI: mix Codex, Claude Code, Hermes, OpenCode and 8 more in one workspace | -| Claude Squad / amux / Conductor | Parallel agent runners with git worktree isolation | Evidence-backed review (Finding → Evidence → Decision → Disposition), not just parallel execution | -| CrewAI / AutoGen / LangGraph | Programmable multi-agent frameworks you build yourself | Ready-to-use desktop workflow — no orchestration code to write | -| Conductor (conductor.build) | macOS desktop for parallel Claude Code + Codex | Heterogeneous CLI support (12+ agents), evidence trails, human gate before writes | -| Emdash | Electron desktop for 22+ CLI agents | Decision traceability, evidence-aware runs, structured adoption records | -| Bernstein | Deterministic orchestrator with pre-merge verification | Human-in-the-loop adoption gate, not just automated CI checks | -| Buzz / Pragma / Paperclip | Agent communication / workflow / org management | Case-scoped independent judgments with evidence-backed decisions, not identity or org charts | -| Warp Oz / Devin / Factory / OpenHands Cloud | Cloud-hosted agent execution platforms | Runs locally in your Electron work cell with existing CLIs — no cloud dependency | +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. -## See it in action +## General Agent catalog -| Local Agent discovery | -Multi-agent review | -Direct multimodal work | -
|---|---|---|
![]() |
- ![]() |
- ![]() |
-
下载 Meldwork V1.0.5 Apple 芯片 macOS 版 @@ -26,68 +20,49 @@ · 许可证
-## 适合谁 +## Meldwork 适合什么工作 -当你有以下需求时,Meldwork 更适合: +当一个决定需要多个视角,并且需要留下清晰的采用依据时,Meldwork 更适合: -- 已经安装多个本地 Agent CLI,希望让同一任务跨 Agent 协作; -- 需要在代码评审、研究或产品分析中获得独立判断,再选择方案; -- 需要在写入工作区前检查可追溯的运行轨迹、证据并保留人工复核。 +- 研究与信息综合:结合本地 Agent 工具和明确选择的知识源; +- 产品、市场、运营和技术分析; +- 写作、规划、评审和结构化文档工作; +- 处理本地文档、图片、音频、视频、PDF、代码和配置文件的多模态工作; +- 需要保留发现、证据、权限、运行轨迹和最终采用决定的实施工作。 -## 工作流程 +## 一个任务如何在 Meldwork 中推进 -1. **选择**本地 Agent 和参与者。 -2. **限定**目标、工作目录、上下文和权限。 +1. **选择**本 Case 的 Agent 和参与者。 +2. **限定**目标、工作目录、上下文、附件、Skill、知识源和权限。 3. **运行**直接会话、并发回复或 Auto Discussion V4。 -4. **复核并采用**结果、证据和待处理的人工审批门(Human Gate),再写入工作区。 +4. **复核**发现、证据、产物、运行轨迹和人工审批门。 +5. **采用**批准的结果,或保留为待解决状态继续处理。 ## 协作模式 | 模式 | 运行方式 | 适合场景 | | --- | --- | --- | -| **直接会话** | 一个已选 Agent 在适配器支持时保持对话和原生会话。 | 使用单个 Agent 完成聚焦工作。 | -| **并发回复** | 已选 Agent 收到同一份冻结任务快照,并按稳定顺序返回独立回复。 | 在选择方案前比较不同路径。 | -| **Auto Discussion V4** | 首轮并发提案。后续轮次由 Agent 根据讨论结果通过最后一行的 `@Agent` 决定下一位参与者;@ 一个 Agent 时单独运行,@ 多个 Agent 时并发运行。每个 Agent 在同一任务中持续使用原生会话。 | 需要讨论、灵活分工和复核的多轮工作。 | +| **直接会话** | 一个已选 Agent 在适配器支持时保持对话和原生会话。 | 聚焦研究、写作、分析或执行。 | +| **并发回复** | 已选 Agent 收到同一份冻结任务快照,并按稳定顺序返回独立回复。 | 在选择方案前比较不同视角。 | +| **Auto Discussion V4** | Agent 先提出方案,再进行质询、职责协商、分工执行、候选结果整合和独立复核;支持时会在多轮中保持原生会话。 | 需要讨论、分工和复核的多步骤工作。 | -参与者始终由用户选择。从更大候选池自动选人不属于当前预览版。 +参与者始终由用户选择。从更大候选池自动选人组队不属于当前预览版。 -## Meldwork 与相邻产品的区别 +## 复核记录 -Meldwork 是面向多 Agent 评审与决策可追溯性的本地优先 AI Agent 工作空间,不是终端、云端 Agent Fleet、通信网络或可编程编排框架。它把你已经在使用的本地 Agent 工具连接到可形成决定的评审流程,并在一个本地工作单元中保留独立发现、证据、责任和人工采用决定。 +Meldwork 将协作组织成一套决策过程,而不是一串聊天消息: -| 项目 | 类别 | 主要解决什么 | Meldwork 的区别 | -| --- | --- | --- | --- | -| [Buzz](https://github.com/block/buzz) | Agent 通信网络 | 身份、频道、事件和持续协作。 | 面向单个 Case 的独立判断,以及有证据支持的 Decision 和 Disposition。 | -| [Pragma](https://github.com/pqpo/pragma) | 方法与工作流运行时 | 可复用的 Expert、Flow、Memory、Evaluation 和 DSL 资产。 | 在流程固定前保留分歧、复验和采用记录。 | -| [Munder Difflin](https://github.com/chaitanyagiri/munder-difflin) | 可视化 Agent 公司 | Boss -> Manager -> Workers,以及任务和活动状态。 | 追踪 Finding -> Evidence -> Decision -> Disposition,不让中心经理隐藏分歧。 | -| [Superset](https://github.com/superset-sh/superset) / [Conductor](https://www.conductor.build/) / [Vibe Kanban](https://github.com/BloopAI/vibe-kanban) | 并行编码工作台 | 并行 Coding Agent、隔离工作区、Diff 和 Merge。 | 面向异构 CLI 的本地优先评审,不以终端数量、Worktree 吞吐量或云 Sandbox 竞争。 | -| [cmux](https://github.com/manaflow-ai/cmux) | Agent 原生终端 | 低摩擦终端、通知和多任务处理。 | 增加冻结上下文、独立结果和人工采用门。 | -| [Nimbalyst](https://github.com/nimbalyst/nimbalyst) | Agent 与 Artifact 工作空间 | 并行 Agent,以及 Markdown、Mockup 和 Diagram。 | 在 Artifact 旁边保留证据和可追责的决定。 | -| [Paperclip](https://github.com/paperclipai/paperclip) | Agent 组织管理 | 公司、岗位、预算、审批和组织图。 | 将责任落在真实 Finding 和结果上,而不是虚拟公司。 | -| [MCP Agent Mail](https://github.com/Dicklesworthstone/mcp_agent_mail) | Agent 通信基础设施 | 身份、收件箱、Thread 和 advisory file lease。 | 在传输层之上保留 Case 和评审语义。 | -| LangGraph / CrewAI / AutoGen / OpenAI Agents SDK / Google ADK | 可编程多 Agent 框架 | 面向开发者的 Graph、角色、路由、工具和审批。 | 团队无需编写编排框架代码即可获得桌面评审流程。 | -| Warp Oz / Devin / Factory / OpenHands Cloud | 云端 Agent 控制面 | 托管 Sandbox、远程执行和 Agent Fleet。 | 在本地 Electron 工作单元中使用现有 CLI,并保持本地数据边界。 | +- **Case**:定义问题、范围、上下文和权限; +- **Finding**:记录 Agent 的判断、观察或行动建议; +- **Evidence**:将 Finding 连接到回复、产物、文件、知识结果或其他受约束的依据; +- **Decision**:记录证据支持的结论、未决问题和选定路径; +- **Disposition**:记录结果已接受、修订、拒绝、被替代或仍未解决。 -## 运行示例 +Run Ledger 会保留阶段、参与者、尝试、回执、产物、恢复状态和人工审批门。诊断工具输出与敏感运行信息留在 Electron 主进程边界内。 -| 本地 Agent 检测 | -多 Agent 评审 | -直接会话中的多模态工作 | -
|---|---|---|
![]() |
- ![]() |
- ![]() |
-