自定通用包装价值有限，任务专用包装更有意义
Jerry Liu 说通用 harness 不如任务专用，先用 Codex/Claude Code 打底再蒸馏，实践性很强。
Jerry Liu 认为创建自定义通用 harness 价值不大，但针对特定任务的自定义 harness 可以满足准确性/成本/延迟等生产约束，例如编码领域先验、模型混合和 UX。
他建议先用 Codex 或 Claude Code 引导工作流，然后蒸馏成更具体的实现。相比通用智能体提示，任务专用方案效果更好。
I don't think there's a ton of value in creating custom general harnesses. But there will always tremendous value in creating custom task-specific harnesses, especially if you need to satisfy accuracy/cost/latency constraints for production. You can encode all the domain-specific priors, the right model mixture, and the right UX so it's far better than you trying to prompt a general agent with some skills/prompts. 1. You can always bootstrap any workflow with Codex/Claude Code first 2. Distill it into something more specific Ishan @radshaan Is there even a point in creating a custom harness anymore? I feel like Codex/Claude Code/Open Code/etc. have all implemented the hard parts correctly and we should just use coding harnesses as general purpose harnesses 🔗 View Quoted Tweet📊 2 ⚡
This report is categorized under AITOP's "How-to" desk. Within our cross-regional analytical framework, it directly maps to AI developer toolchains, coding agents, and engineering workflows. Key entities and technical topics under continuous tracking include Codex, Claude Code, coding assistants, workflows.
Source attribution: curated from Jerry Liu (@jerryjliu0).
