
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 分