Cost & token efficiency
One qualified GitHub discussion points to this friction. Use the plan below to test it with practitioners before building.
Where this need appears
Each item below is a public, qualified GitHub discussion. The Radar groups related friction, while the original Issue remains available for source checking.
- Logs about token consumption (too many tokens are burned)HKUDS/nanobot · 14 comments · 0 positive reactions
Turn the signal into one observable action
Instrument one representative workflow, remove or cache its highest-cost repeated step, then replay the same task set against the original baseline.
Median cost falls by a written target across at least five comparable runs without reducing completion quality.
Ask before you build
- Show the cost or token trace for one completed task.
- Which step consumes the largest share?
- How often is context or work repeated?
- What quality level must remain unchanged?
- What monthly limit would make this sustainable?
Professional guardrail: Measure repeated use and time returned across two cycles, not a one-time demo completion.
Choose a narrow next move
Save this pattern in the free workspace, interview someone who recently hit it, and record one concrete commitment or decision. Do not treat issue counts or compliments as willingness to pay.