
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Isomoes Blog</title>
      <link>https://isomoes.github.io/zh/blog</link>
      <description>Isomoes personal blog</description>
      <language>zh-cn</language>
      <managingEditor>jiahaoxiang2000@gmail.com (Isomoes)</managingEditor>
      <webMaster>jiahaoxiang2000@gmail.com (Isomoes)</webMaster>
      <lastBuildDate>Sun, 19 Apr 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://isomoes.github.io/zh/tags/multi-agent/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://isomoes.github.io/zh/blog/tools/ai-agent-own-what-we-owned</guid>
    <title>AI Agent 应该接管那些原本由我们自己承担的部分</title>
    <link>https://isomoes.github.io/zh/blog/tools/ai-agent-own-what-we-owned</link>
    <description>vibe coding 的下一步，不是彻底移除人类，而是尽量把人从每个内部开发循环里移出去。当 agent 能自己完成更多验证时，多 agent 系统就不会继续被同一个人卡住。</description>
    <pubDate>Sun, 19 Apr 2026 00:00:00 GMT</pubDate>
    <author>jiahaoxiang2000@gmail.com (Isomoes)</author>
    <category>ai-agent</category><category>vibe-coding</category><category>multi-agent</category><category>chrome-devtools-mcp</category><category>verification</category><category>workflow</category>
  </item>

  <item>
    <guid>https://isomoes.github.io/zh/blog/tools/ai-agent-token-plan</guid>
    <title>如何为 AI Agent 选择 Token 方案</title>
    <link>https://isomoes.github.io/zh/blog/tools/ai-agent-token-plan</link>
    <description>对 AI agent token 获取的两条主要路径进行实际分析——按量付费的 API 方式与订阅制的代码计划——附真实成本数据，并根据单 agent 还是多 agent 场景给出具体建议。</description>
    <pubDate>Tue, 31 Mar 2026 00:00:00 GMT</pubDate>
    <author>jiahaoxiang2000@gmail.com (Isomoes)</author>
    <category>ai-agent</category><category>token</category><category>pricing</category><category>claude-code</category><category>codex</category><category>openrouter</category><category>multi-agent</category><category>budget</category>
  </item>

  <item>
    <guid>https://isomoes.github.io/zh/blog/tools/four-layer-multi-agent-workflow</guid>
    <title>终于在预算内跑起来的四层多 Agent 工作流</title>
    <link>https://isomoes.github.io/zh/blog/tools/four-layer-multi-agent-workflow</link>
    <description>面向刚接触 agent coding 的读者，介绍我们最新的四层多 agent 工作流：更便宜的模型访问、OpenCode runtime、Superpowers 自动化，以及 iKanban 审查界面。</description>
    <pubDate>Sat, 21 Mar 2026 00:00:00 GMT</pubDate>
    <author>jiahaoxiang2000@gmail.com (Isomoes)</author>
    <category>multi-agent</category><category>workflow</category><category>opencode</category><category>superpowers</category><category>ikanban</category><category>codex</category><category>ai-coding</category><category>budget</category>
  </item>

  <item>
    <guid>https://isomoes.github.io/zh/blog/tools/vibe-kanban-intro</guid>
    <title>Vibe-Kanban：编排多 Agent AI 编程工作流</title>
    <link>https://isomoes.github.io/zh/blog/tools/vibe-kanban-intro</link>
    <description>一篇关于 vibe-kanban 的完整指南：它是一个开源编排平台，用于管理多个 AI 编程 agent。本文会介绍如何设置 workspace、配置基于 OpenCode 和 Claude Code 的多模型 profile，并提升整体开发效率。</description>
    <pubDate>Wed, 28 Jan 2026 00:00:00 GMT</pubDate>
    <author>jiahaoxiang2000@gmail.com (Isomoes)</author>
    <category>vibe-kanban</category><category>multi-agent</category><category>ai-coding</category><category>parallel-workflow</category><category>opencode</category><category>claude-code</category><category>productivity</category><category>task-scheduling</category>
  </item>

  <item>
    <guid>https://isomoes.github.io/zh/blog/tools/multi-agent-parallel</guid>
    <title>多 Agent 并行工作流：从写代码的人到指挥调度者</title>
    <link>https://isomoes.github.io/zh/blog/tools/multi-agent-parallel</link>
    <description>分享我第一次使用 vibe-kanban 和 OpenCode 进行多 agent 并行工作流的体验。学会把任务拆解后交给 AI 并行执行，生产力会大幅提升，开发者的角色也会从编码者转向编排者。</description>
    <pubDate>Fri, 16 Jan 2026 00:00:00 GMT</pubDate>
    <author>jiahaoxiang2000@gmail.com (Isomoes)</author>
    <category>multi-agent</category><category>opencode</category><category>vibe-kanban</category><category>parallel-workflow</category><category>ai-coding</category><category>productivity</category><category>task-scheduling</category>
  </item>

    </channel>
  </rss>
