需求卡片 #256 · 相关性 高 · 新发现

Strands Harness 成本与定制化痛点

更新于 2026/9/29 22:11:51

问题概述

用户担忧在使用非原生 harness 时需频繁评估每个模型发布的兼容性,且对成本高且基准测试饱和的情况缺乏更便宜的替代方案;同时对定制化能力和系统提示冗余表示不满。

痛点标签

待验证问题

证据

原话 · @Anonymous
I am increasingly hesitant to use non-native harnesses - model providers are now starting to train their agents for use within the harness. An eval like terminal bench can only capture so much data. I don't want to have to assess each harness every model release to make sure it's working as well as it can.
原话 · @Anonymous
Why is Pi not in the benchmarks? Deepseek beats Strands and its built on Pi so that’s all I needed to know.
原话 · @Anonymous
> With Fable 5, Strands harness cost 77% less than Claude Code and scored higher on Terminal Bench 2.1.Terminal Bench 2.1 is saturated. Many token saving techniques would save money and score basically the same running Fable 5 against Terminal Bench 2.1. (They claim a better score but don’t say how much better. I’d bet my favorite hat that it’s not statistically significant.)This is at least the fourth time I’ve seen a project hit front page with a “save money with same score on saturated benchmark” claim.
原话 · @Anonymous
I remember reading about strands SDK and it looked great in terms how everything is an event that you can extend, so this harness feels quite about right. However, for this kind of customisation, Pi is actually quite great. One of the most things I love about Pi is ability to ask it to create an extension and it does it quite well as it’s part of their docs. Also ability to customise the system prompt to avoid the clutter that Claude Code add (around 20k system prompt that mostly had nothing to do with the code).

免责声明:本卡片由 AI 从社区讨论中提炼,属于「痛点证据」,是需求分析与验证的起点,不等同于「已验证的市场需求」。AI 存在分析局限,关键决策前请打开上方原始讨论人工复核。