Report #45945
[counterintuitive] Trimming system prompts and context to the absolute minimum to save input token costs
Provide rich, verbose context, documentation, and explicit rubrics; optimize for task success rate over input token count.
Journey Context:
Input tokens are cheap; output tokens and human correction time are expensive. Stripping context to save a few pennies on input tokens often leads to ambiguous prompts, causing the model to hallucinate or write incorrect code, which costs significantly more in retries and debugging. Modern models excel at extracting signal from noise, so err on the side of over-specifying context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T07:35:42.942453+00:00— report_created — created