[{"data":1,"prerenderedAt":158},["ShallowReactive",2],{"category-data-workflow":3},[4],{"id":5,"title":6,"body":7,"description":143,"extension":144,"meta":145,"navigation":153,"ogImage":147,"path":154,"seo":155,"stem":156,"__hash__":157},"content/blogs/4. Agent 相关的折腾记录（持续更新）.md","Agent 相关的折腾记录（持续更新）",{"type":8,"value":9,"toc":127},"minimark",[10,14,18,21,24,29,32,36,39,43,46,50,53,57,60,64,67,70,73,77,90,112],[11,12,13],"h2",{"id":13},"背景",[15,16,17],"p",{},"最近终于静下心来认真研究 Agent 生态。在此之前一直没下场深入折腾，主要是觉得这个领域生态变化太快、技术栈也不够成熟，迭代节奏完全跟不上。直到最近，Agent 相关的概念（Tools、MCP、Skills、Subagents、Hooks 等）逐渐收敛到一个相对稳定的形态，于是开始全面尝试。",[11,19,20],{"id":20},"介绍一下我有哪些工具",[15,22,23],{},"截至目前，我体验过 Claude Code、Codex、Cursor，最近还试用了 SOLO Trae（支持国产）。下面分别说一下感受。",[25,26,28],"h3",{"id":27},"claude-code","Claude Code",[15,30,31],{},"目前我用过编程体验最好的一个 Agent。聪明程度在一众 Coding Agent 里算是天花板级别，插件生态成熟，可以与 Cursor / VSCode 等编辑器协同使用：在终端里启动 Claude Code 后，能直接选中编辑器里的某段代码作为上下文同步过去；它给出的修改建议也能在编辑器里直观地 review 与 apply，整体闭环非常顺滑。",[25,33,35],{"id":34},"codex","Codex",[15,37,38],{},"量大管饱，模型水平也相当能打，开 high reasoning 写代码完全顶得住。相比之下生态略弱一些，更偏\"原生 IDE 助手\"路线。",[25,40,42],{"id":41},"cursor","Cursor",[15,44,45],{},"中规中矩。用 GPT 系列经常出现\"降智\"，Claude Sonnet 与 Opus 又容易过度思考；简单任务用 auto 模式既快又便宜。Tab 补全确实惊艳，对于\"手写古人\"来说值得一试。",[25,47,49],{"id":48},"solo-trae","SOLO Trae",[15,51,52],{},"目前模型免费，可以用来跑一些轻量任务。问题在于自定义模型能力较弱、调用 Skill 还需要显式指定，加之经常需要排队，整体体验仍有较大提升空间。",[11,54,56],{"id":55},"skills","Skills",[15,58,59],{},"最近发现 Skills 能显著扩展模型的能力边界——它本质上是一份\"在特定场景下注入到上下文的提示词包\"，让 Agent 在面对垂直任务时能够直接调用既定的方法论与工具链。后续打算系统挖掘一下 Skills 的设计模式与最佳实践。",[11,61,63],{"id":62},"mcp","MCP",[15,65,66],{},"MCP（Model Context Protocol）方面体验还不算多。目前高频使用的是 Notion 的 MCP，可以让 AI 直接把整理好的内容写入 Notion 工作区，大大减少了\"复制 → 粘贴 → 排版\"的人肉环节。",[11,68,69],{"id":69},"杂谈",[15,71,72],{},"我还使用 CC-Switch 来管理多个 API 渠道。Claude Code 的主力渠道是公益站 AnyRouter，唯一的痛点是稳定性偏弱；不过最近恢复正常了，准备再战一波。",[11,74,76],{"id":75},"zcf","ZCF",[15,78,79,80,84,85,89],{},"ZCF，全称 ",[81,82,83],"strong",{},"Zero-Config Code Flow","，是一个面向专业开发者的 CLI 工具，目标是在几分钟内完成 Claude Code 与 Codex 的端到端环境初始化。通过 ",[86,87,88],"code",{},"npx zcf"," 即可一站式完成：配置目录创建、API/代理接入、MCP 服务接入、工作流导入、输出风格与记忆配置，以及常用工具安装。",[15,91,92,93,96,97,100,101,104,105,108,109,111],{},"最近体验了一下 ",[86,94,95],{},"zcf:init-project","，发现确实比 Claude Code 与 Codex 自带的 ",[86,98,99],{},"init"," 强不少。它会生成总体级与目录级的 ",[86,102,103],{},"CLAUDE.md"," 作为指导文件，还会生成 ",[86,106,107],{},".claude/index.json"," 作为文件索引并记录修改时间；之后每次用 Claude Code 修改代码，都会顺带同步更新 ",[86,110,103],{},"，把\"何时改了什么\"完整记录下来。这种做法极大提升了 AI 代码的可维护性，避免出现\"AI 拉了一大坨，谁也不敢动\"的局面。代价是会增加 token 消耗，但在我看来收益远大于成本。",[15,113,114,115,118,119,122,123,126],{},"zcf 在安装时还可以可选地安装一些 MCP 服务。我个人常用的组合是 ",[81,116,117],{},"spec-workflow","、",[81,120,121],{},"context7"," 与 ",[81,124,125],{},"open-websearch"," 这三个，不过最近 spec-workflow 经常连不上，后面要找时间排查一下。",{"title":128,"searchDepth":129,"depth":129,"links":130},"",2,[131,132,139,140,141,142],{"id":13,"depth":129,"text":13},{"id":20,"depth":129,"text":20,"children":133},[134,136,137,138],{"id":27,"depth":135,"text":28},3,{"id":34,"depth":135,"text":35},{"id":41,"depth":135,"text":42},{"id":48,"depth":135,"text":49},{"id":55,"depth":129,"text":56},{"id":62,"depth":129,"text":63},{"id":69,"depth":129,"text":69},{"id":75,"depth":129,"text":76},"记录自己折腾一些智能体相关技术的经历","md",{"date":146,"image":147,"alt":148,"tags":149,"published":153},"30 April 2026","/blogs-img/blog4.jpg","Agent",[148,150,151,63,56,152],"折腾笔记","workflow","harness",true,"/blogs/agent",{"title":6,"description":143},"blogs/4. Agent 相关的折腾记录（持续更新）","vjEXzDqS_QflOdiOb0-sVscMDQi_vUJbVilrm2BCLNM",1777822134947]