
Agenttrio
io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Nov 3, 2026
有界的規劃者-編碼者-審查者工作流:狀態、已驗證執行和已設定檢查。
AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。
原文描述
Bounded planner-coder-reviewer workflows: status, verified run, and configured checks.
概覽
Agenttrio 的本機 MCP 服務;無需登入;STDIO。
暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Agenttrio,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
agenttrio
agenttrio runs bounded agent workflows made of three roles — a planner, a coder, and a separate read-only reviewer — against a local Ollama backend. It reports the workspace status, runs one task through the trio behind a host-enforced verification gate, and runs the workspace's configured checks. One binary serves a command-line interface and a stdio MCP server with exactly three tools.
Work is bounded by the operator config: model turns per role,
coder → verification → reviewer cycles, total tool calls, and
context size all have explicit budgets, and a run is only
verified when the gate below passes — never on the model's say
alone.
Configuration
agenttrio reads an operator-reviewed TOML file. Passing --config <file> explicitly approves loading that file; a workspace
config.toml or .flow.toml is never auto-loaded. The only
auto-loaded location is $XDG_CONFIG_HOME/flow/config.toml.
Notes that matter:
- Check
timeoutvalues are milliseconds; the Ollamatimeoutis seconds. --workspaceoverrides the config's workspace, and--modeloverrides every role's model.- A non-loopback Ollama endpoint is refused unless the config sets
ollama.allow_remote = true. - Default mode is read-only.
runandcheckrequire--trusted, which is what allows project edits and explicitly configured named checks. - With no resolvable configuration, every command fails with an error naming the missing configuration — nothing is invented.
- Ollama itself is external: run
ollama serveand pull a tool-capable model (for exampleollama pull qwen2.5-coder:7b) before expecting runs to work.
Install
Or run the container image:
The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead; mount your config and workspace into the container if you use it that way.
CLI
Reports print as JSON. Exit codes follow the documented scheme:
0 on success, 1 for a runtime failure (including an
unverifiable run configuration), and 2 for usage errors.
Arguments are validated before any configuration is read, so a
malformed invocation is always a usage error.
The verification gate
A run is reported verified: true only when all of these hold:
- the planner and coder complete within their budgets;
- at least one required named check runs, and every required check passes;
- a separate read-only reviewer returns structured approval (a
JSON object with
"approved": true).
If the gate fails, the cycle repeats (coder → checks → reviewer)
up to max_cycles, and the final report says verified: false
with a note naming which condition failed.
MCP server
One bin serves both faces. The mcp subcommand starts a stdio
MCP server (newline-delimited JSON-RPC):
MCP client configuration:
Replies carry the report as a JSON text block plus
structuredContent; failures are returned as isError results.
The server is deliberately sequential.
Tools
The tool list is intentionally only these three tools.
Development
License
MIT — see LICENSE.
來源:README.md,提交 37a0ad1
工具
0版本歷史
1- v0.1.0最新Nov 3, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分