2026-08-22
每日一文 · 长文精读
Cloudflare Cuts Astro Github Issues by 85% with AI Agents
Cloudflare 借助 AI 代理将 Astro 的 GitHub 问题减少 85%
作者：Leela Kumili · InfoQ 原文
摘要：Cloudflare 使用在 GitHub Actions 中运行的隔离 AI 代理，自动化了 Astro 开源框架的问题分类流程。该工作流重现报告的错误、诊断根本原因、验证行为并提出修复方案，然后生成预览版本供报告者验证。Astro 的开放问题数从 200 多个降至约 30 个，减少了约 85%。工作流通过状态机驱动，代理之间通过 report.md 文件传递信息。Cloudflare 还将失败的代理运行视为代码库可维护性的信号。该工作流后来成为独立的 GitHub Action triagebot-action，其编排模型演变为开源框架 Flue。
Cloudflare has automated issue triage for the Astro open source framework using isolated AI agents running in GitHub Actions.
Cloudflare 使用在 GitHub Actions 中运行的隔离 AI 代理，自动化了 Astro 开源框架的问题分类流程。
The workflow reproduces reported bugs, diagnoses root causes, verifies behavior, and proposes fixes before generating preview releases for reporters to validate.
该工作流重现报告的错误、诊断根本原因、验证行为并提出修复方案，然后生成预览版本供报告者验证。
Cloudflare reports that Astro's open issue count fell from more than 200 to about 30, an approximately 85% reduction based on those figures, with the team targeting zero open issues.
Cloudflare 报告称，Astro 的开放问题数从 200 多个降至约 30 个，基于这些数字减少了约 85%，团队的目标是实现零开放问题。
The workflow mirrors the steps Astro maintainers followed during manual issue resolution.
该工作流模仿了 Astro 维护者在手动解决问题时遵循的步骤。
Each stage runs as a separate subagent.
每个阶段作为独立的子代理运行。
A reproduction agent verifies the reported behavior, a diagnosis agent instruments the code to identify the cause, a verification agent examines tests, documentation, and comments, and a fix agent converts the reproduction into tests before implementing a solution.
重现代理验证报告的行为，诊断代理检测代码以确定原因，验证代理检查测试、文档和评论，修复代理在实施解决方案前将重现转化为测试。
Agents pass information through a report.md file rather than sharing a single execution context.
代理通过 report.md 文件传递信息，而不是共享单个执行上下文。
Cloudflare implemented the workflow as a state machine driven by GitHub issue labels.
Cloudflare 将工作流实现为由 GitHub 问题标签驱动的状态机。
New issues receive a triage needed label, while confirmation of a proposed fix moves an issue toward fix verified.
新问题会收到“需要分类”标签，而对提议修复的确认会将问题推向“修复已验证”。
When an agent identifies a potential fix, the workflow creates a preview release and posts findings, logs, and installation instructions to the issue.
当代理识别出潜在修复时，工作流会创建预览版本，并将发现、日志和安装说明发布到该问题中。
After the reporter validates the patch, the automation opens a pull request.
在报告者验证补丁后，自动化会打开一个拉取请求。
A July 2026 Astro issue involving the Container API, for example, was marked triage: fix verified after the reporter confirmed the bot's fix.
例如，2026 年 7 月一个涉及 Container API 的 Astro 问题，在报告者确认机器人的修复后被标记为“分类：修复已验证”。
Thrives wrote in a LinkedIn comment that the significance is not simply having AI verify an issue, but running agent work in a sandbox so human reviewers primarily see results that have passed through the automated process.
Thrives 在 LinkedIn 评论中写道，其意义不仅仅是让 AI 验证问题，而是在沙箱中运行代理工作，以便人工审查者主要看到已通过自动化流程的结果。
Jordan Matthiesen, Senior Product Manager at CloudBees, similarly highlighted reproduction before diagnosis and making fixes easy for reporters to test, while Shubhanshu Singh described the workflow as an example of explicit agent system design.
CloudBees 高级产品经理 Jordan Matthiesen 同样强调了在诊断前进行重现，并使修复易于报告者测试，而 Shubhanshu Singh 则将工作流描述为显式代理系统设计的一个例子。
Cloudflare also treats failed agent runs as signals about codebase maintainability.
Cloudflare 还将失败的代理运行视为关于代码库可维护性的信号。
In one Hot Module Replacement case, an agent repeatedly modified a conditional and introduced regressions because the behavior lacked sufficient tests.
在一个热模块替换案例中，代理反复修改了一个条件并引入了回归，因为该行为缺乏足够的测试。
Adding a descriptive code comment changed the agent's behavior and prevented the repeated modification.
添加描述性的代码注释改变了代理的行为，并防止了重复修改。
The Astro workflow later became triagebot-action, a standalone GitHub Action, while its orchestration model evolved into Flue, an open-source framework for building durable agent workflows.
Astro 工作流后来成为 triagebot-action，一个独立的 GitHub Action，而其编排模型演变为 Flue，一个用于构建持久代理工作流的开源框架。
Flue uses a declarative model in which developers define an agent's context, including its model, skills, sandbox, and instructions, rather than writing an orchestration loop.
Flue 使用声明式模型，开发者定义代理的上下文，包括其模型、技能、沙箱和指令，而不是编写编排循环。
Its execution history is persisted through an append-only event log, allowing an interrupted workflow to resume from its previous state.
其执行历史通过仅追加的事件日志持久化，允许中断的工作流从之前的状态恢复。
Flue can integrate agents with GitHub, Slack, Linear, and Discord and can run on Node.js, GitHub Actions, or Cloudflare infrastructure.
Flue 可以将代理与 GitHub、Slack、Linear 和 Discord 集成，并可以在 Node.js、GitHub Actions 或 Cloudflare 基础设施上运行。
On Cloudflare, agents can run as Durable Objects with durable execution and isolated storage.
在 Cloudflare 上，代理可以作为 Durable Objects 运行，具有持久执行和隔离存储。
The Astro triage workflow therefore provides one example of a broader Flue model in which bounded agent tasks, persistent state, external events, and human approval points form a durable software workflow.
因此，Astro 分类工作流提供了更广泛 Flue 模型的一个例子，其中受限的代理任务、持久状态、外部事件和人工审批点形成了持久的软件工作流。
阅读理解
1. What is the primary benefit of using isolated AI agents in the Astro issue triage workflow?
2. How does Cloudflare treat failed agent runs in the context of the Astro workflow?
3. What is the role of the 'report.md' file in the Astro AI issue triage workflow?