OnlyTerp Target
Which harness, which file, which lines. Cite a permalink to the relevant code at the audit commit.
Symptom
What's broken in the user's current setup. Be concrete:
- Which API call is wrong
- What field is missing/wrong/volatile
- What
usagefield comes back zero or wrong
Fix
--- a/path/to/file.ts
+++ b/path/to/file.ts
@@
- old line
+ new line
If the fix is multi-step or conditional, list the steps.
Verify
After applying, the agent should:
- Run
<command>to exercise the code path. - Capture the wire (mitmproxy or harness debug log).
- Confirm
<specific assertion>— e.g.usage.cache_read_input_tokens > 0on the second turn.
If the assertion fails, the fix didn't land or there's a second upstream issue. Stop and report.
Background
Why this matters in 1-2 sentences. Link to:
- [docs/concepts/.md] for the API mechanics
- [docs/gotchas.md#N] for the underlying footgun
- [audits/.md] for the full audit