# agent-cluster **Repository Path**: liu-ritian/agent-cluster ## Basic Information - **Project Name**: agent-cluster - **Description**: 一个零依赖、面向本地运行的多模型 agent 集群工作台。它提供图形化配置界面、任务编排、工作区工具调用,以及会话级运行时观测能力。 - **Primary Language**: Unknown - **License**: MIT - **Default Branch**: main - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 1 - **Forks**: 0 - **Created**: 2026-04-02 - **Last Updated**: 2026-04-18 ## Categories & Tags **Categories**: Uncategorized **Tags**: agent集群 ## README # Agent Cluster Workbench
Desktop-first multi-model agent cluster runtime for controller-led orchestration, capability-aware delegation, traceable workspace execution, and packaged local delivery. [Root Landing README](./README.md) | [Simplified Chinese](./README.zh-CN.md)

Node.js License Desktop Runtime Observability

## Overview Agent Cluster Workbench is a local-first desktop control plane for running coordinated controller, leader, worker, and child-agent workflows across multiple model providers. It is built as runtime infrastructure rather than a thin prompt wrapper: tasks are routed by scheme, bounded by tool and role policies, observed through live traces, and delivered through a Windows desktop package. ## At A Glance | Dimension | Summary | | --- | --- | | Runtime shape | Controller-led multi-agent orchestration with staged execution | | Execution stages | Research, implementation, validation, handoff | | Observability | Live status feed, Task Trace, call chain, virtual cluster graph | | Safety model | Capability-aware routing, child-agent inheritance, task-scope guards | | Runtime state | Session memory, retry, fallback, circuit breaker, cost estimates | | Delivery target | Local web console and packaged `dist/AgentClusterWorkbench.exe` | ## Capability Matrix | Capability | Included | | --- | --- | | Controller / leader / worker delegation | Yes | | Child-agent inheritance of enabled capabilities | Yes | | Workspace file and command tool layer | Yes | | Task Trace and call-chain visualization | Yes | | Session memory, token usage, cost summaries | Yes | | Retry, fallback, circuit breaker | Yes | | Per-model Thinking mode toggle | Yes | | Web-search capability verification | Yes | | Chinese / English runtime UI | Yes | | Task log export and post-run cleanup | Yes | | Windows EXE packaging | Yes | ## Module Layers ```text UI Layer src/static/ web UI, trace panels, connectivity console, agent graph, chat pane Runtime Orchestration src/cluster/ controller planning, staged routing, delegation, synthesis src/session/ trace spans, session memory, retries, cost accounting Execution Adapters src/providers/ OpenAI / Anthropic / Kimi-compatible adapters src/workspace/ file tools, command policy, artifact generation Server / Packaging src/http/ API routes for settings, runs, tests, logs scripts/ packaging, verification, syntax checks ``` ## Execution Flow ```mermaid flowchart TD UI[Desktop Console] CFG[Scheme and Model Config] CTRL[Controller] PLAN[Planning] LEAD[Phase Leaders] WORK[Workers and Child Agents] WS[Workspace Tool Layer] TRACE[Trace, Session, Cost] LOG[Task Logs] OUT[Final Synthesis] UI --> CFG CFG --> CTRL CTRL --> PLAN PLAN --> LEAD LEAD --> WORK WORK --> WS CTRL --> TRACE LEAD --> TRACE WORK --> TRACE WS --> TRACE TRACE --> LOG WORK --> OUT LEAD --> OUT CTRL --> OUT OUT --> UI ``` ## Quick Start ```powershell npm install npm start ``` Development mode: ```powershell npm run dev ``` Default address: ```text http://127.0.0.1:4040 ``` ## Validation Run the full validation suite: ```powershell npm test ``` Run focused checks: ```powershell npm run test:smoke npm run test:unit npm run check ``` The left-side connectivity panel validates three paths independently: - basic reply - web-search execution - Thinking-mode execution ## Kimi / Kimi Code Web Search Setup - `Kimi Chat`: use provider `kimi-chat` with `Base URL` set to `https://api.moonshot.cn/v1`. When `Allow Web Search` is enabled, the runtime turns on Moonshot's built-in `$web_search` tool and disables Thinking automatically for compatibility. - `Kimi Coding` / `Kimi Code`: use provider `kimi-coding` with `Base URL` set to `https://api.moonshot.cn/anthropic`, not the older `/v1` route. When `Allow Web Search` is enabled, the runtime sends the Anthropic-compatible `web_search_20250305` server tool. - Connectivity tests verify real execution paths instead of only checking whether a provider returns a basic response. ## Thinking Mode - `OpenAI Responses`: enabling Thinking sends a `reasoning` payload. If no effort is selected, the runtime defaults to `medium`. - `Claude` / `Kimi Coding`: enabling Thinking sends an Anthropic-compatible `thinking` payload with an effort-mapped budget. - `Kimi Chat`: Thinking works for normal chat requests. If built-in web search is enabled for the same request, the runtime disables Thinking automatically for compatibility. ## Build and Packaging Build the Windows executable: ```powershell npm run build:win-exe ``` Output: ```text dist/AgentClusterWorkbench.exe ``` By default, packaging embeds `cluster.config.blank.json`, not your local `cluster.config.json` or `runtime.settings.json`. If you explicitly override the base config before building, the packaged EXE may include your custom runtime data: ```powershell $env:AGENT_CLUSTER_BASE_CONFIG = "cluster.config.json" npm run build:win-exe ``` ## Privacy and Git Safety The repository ignores local-sensitive runtime artifacts by default, including: - `.env`, `.env.local`, and local environment variants - `cluster.config.json` - `runtime.settings.json` - `dist/runtime.settings.json` - local encryption key files - `workspace/` and `dist/workspace/` - `task-logs/` and `dist/task-logs/` - `bot-connectors/` - `build/sea/` - `dist-verify/` - packaged artifacts such as `dist/*.exe`, `dist/*.zip`, and `dist/*.blockmap` Important: - `runtime.settings.json` stores secrets in encrypted form, but it still should not be committed. - `.gitignore` only protects untracked files. If a sensitive file was tracked earlier, remove it from the Git index first: ```powershell git rm --cached cluster.config.json runtime.settings.json dist/runtime.settings.json dist/AgentClusterWorkbench.exe ``` ## Runtime Characteristics - Controller authority, worker capability, and child-agent inheritance are separated deliberately. - Final deliverables remain while transient cluster artifacts can be cleaned after the run. - Task logs are exported outside the workspace so maintenance data does not pollute delivery outputs. - Connectivity testing checks whether advanced features really execute, not just whether a provider returns a reply. ## FAQ ### Why split controller and worker responsibilities? Planning, delegation, synthesis, and concrete execution fail in different ways and require different capabilities. Separate layers make routing clearer and fallback safer. ### Why test web search and Thinking separately? Because "the model answered" is weaker than "the feature actually executed". This runtime verifies concrete capability paths. ### Will the packaged EXE include my API keys? Not by default. The normal build path embeds `cluster.config.blank.json`, not your local runtime settings. The risk appears only if you explicitly override the base config before packaging. ### Why keep separate language files if the root README is bilingual? The root `README.md` acts as the project landing page. `README.en.md` and `README.zh-CN.md` remain useful as direct links for releases, mirrors, and language-specific sharing. ## Attribution and License - Author: 想画世界送给你 - License: `MIT` - Full text: [LICENSE](./LICENSE)