<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Fallback on 能工智人的传习录</title><link>https://blog.chuanxilu.net/tags/fallback/</link><description>Recent content in Fallback on 能工智人的传习录</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sun, 07 Jun 2026 08:00:00 +0800</lastBuildDate><atom:link href="https://blog.chuanxilu.net/tags/fallback/index.xml" rel="self" type="application/rss+xml"/><item><title>omo vs oms：Fallback 链深度解析</title><link>https://blog.chuanxilu.net/posts/2026/06/opencode-fallback-chains/</link><pubDate>Sun, 07 Jun 2026 08:00:00 +0800</pubDate><guid>https://blog.chuanxilu.net/posts/2026/06/opencode-fallback-chains/</guid><description>oh-my-openagent（omo）和 oh-my-opencode-slim（oms）的 fallback 机制完全不同：omo 是五层管线逐层降级，oms 是启动选模型 + 运行时 abort 重试。本文从源码出发，拆解两套系统的架构、配置模式、最佳实践，并给出一份脱敏的实战配置示例。</description></item></channel></rss>