Cloudflare Cuts Astro Github Issues by 85% with AI Agents Cloudflare 巧用 AI 智能体，将 Astro 项目 GitHub 待办问题削减八成半

Cloudflare has automated issue triage for the Astro open source framework using isolated AI agents running in GitHub Actions. 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 开源框架引入了一套自动化处理机制，借由 GitHub Actions 中运行的独立 AI 智能体，对各类问题进行抽丝剥茧。这套流程能复现报错、探究病灶、校验逻辑，并在给出修复方案后，生成预览版供用户验证。据 Cloudflare 统计，Astro 的待办问题已从两百余个锐减至三十个左右，降幅约达 85%，团队正向着“零待办”的目标迈进。

The workflow mirrors the steps Astro maintainers followed during manual issue resolution. 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.这套流程仿照了 Astro 维护者平日处理问题的章法，将各环节拆解为独立的子智能体。复现智能体负责还原现场，诊断智能体负责剖析代码以寻根究底，校验智能体则审视测试用例、文档与评论，最后的修复智能体将复现过程转化为测试，并落地解决方案。诸智能体之间不共享执行上下文，而是通过一份 report.md 文件传递讯息，各司其职，井然有序。

Astro AI issue triage workflow (Source: Cloudflare Blog Post)Astro AI 问题处理流程图（来源：Cloudflare 官方博客）

Cloudflare implemented the workflow as a state machine driven by GitHub issue labels. 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.Cloudflare 将此流程设计为以 GitHub 标签驱动的状态机。新问题会被贴上“待处理”标签，若修复方案经确认，则流转至“修复已验证”状态。一旦智能体寻得良方，便会生成预览版本，并将日志、安装指南等讯息留于问题下方。待提交者验证无误，自动化程序便会发起合并请求（Pull Request）。例如在 2026 年 7 月处理的一起 Container API 问题中，正是因提交者认可了机器人的修复，该问题才顺利打上“修复已验证”的标签。

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. 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.Thrives 在 LinkedIn 评论中指出，此举的精妙之处不在于 AI 能否验证问题，而在于将智能体置于沙盒中运行，让开发者只需审阅经由自动化流程筛选后的结果。CloudBees 高级产品经理 Jordan Matthiesen 亦有同感，强调应先复现再诊断，并降低用户的测试门槛；Shubhanshu Singh 则称赞该流程是“显式智能体系统设计”的典范。

Jordan Matthiesen, Senior Product Manager at CloudBees, highlighted the importance of reproducing an issue before attempting a diagnosis, making fixes easy for reporters to test, and improving code, tests, and documentation when agents encounter difficulties. Shubhanshu Singh similarly described the Astro workflow as an example of structuring agentic systems through explicit system design rather than relying primarily on agent loop abstractions.Jordan Matthiesen 强调了复现问题对于诊断的先决意义，并指出当智能体遇阻时，应着力优化代码、测试与文档。Shubhanshu Singh 则认为，Astro 的流程胜在通过明确的系统设计来构建智能体架构，而非仅仅依赖智能体循环这一抽象概念。

Astro AI issue triage workflow (Source: Cloudflare Blog Post)

Cloudflare also treats failed agent runs as signals about codebase maintainability. 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.Cloudflare 甚至将智能体执行失败视作 codebase 可维护性的风向标。曾有一例热模块替换（HMR）问题，智能体因缺乏充分的测试，反复修改条件判断反而引入了回归错误。最终，开发者只需补上一段详尽的代码注释，智能体的行为便随之修正，不再重蹈覆辙。

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. 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. Its execution history is persisted through an append-only event log, allowing an interrupted workflow to resume from its previous state.Astro 的处理流程后来演化为独立的 GitHub Action 工具 triagebot-action，其编排模型则蜕变为名为 Flue 的开源框架，专用于构建持久化智能体工作流。Flue 采用声明式模型，开发者只需定义智能体的上下文（含模型、技能、沙盒与指令），无需编写复杂的编排循环。其执行轨迹通过只读日志持久化，纵使工作流中途被打断，亦能从断点处续接。

Flue can integrate agents with GitHub, Slack, Linear, and Discord and can run on Node.js, GitHub Actions, or Cloudflare infrastructure. On Cloudflare, agents can run as Durable Objects with durable execution and isolated storage. 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.Flue 可与 GitHub、Slack、Linear 及 Discord 联动，既能运行于 Node.js 和 GitHub Actions，亦可部署在 Cloudflare 基础设施之上。在 Cloudflare 环境下，智能体能以 Durable Objects 的形式运行，实现持久化执行与隔离存储。Astro 的问题处理流程，恰是 Flue 模型的一个缩影：将受限的任务、持久的状态、外部事件与人工审批点融为一体，铸就了稳固的软件工作流。

About the Author

Leela Kumili

Leela is a Lead Software Engineer at Starbucks with deep expertise in building scalable, cloud-native systems and distributed platforms. She drives architecture, delivery, and operational excellence across the Rewards Platform, leading efforts to modernize systems, improve scalability, and enhance reliability. In addition to her technical leadership, Leela serves as an AI Champion for the organization, identifying opportunities to improve developer productivity and workflows using LLM-based tools and establishing best practices for AI adoption. She is passionate about building production-ready systems, enhancing developer experience, and mentoring engineers to grow in both technical and strategic impact. Her interests include platform engineering, distributed systems, developer productivity, and bridging technical solutions with business and product goals.

Show moreShow less