Report #29416
[counterintuitive] Using complex prompt chaining \(multi-prompt pipelines\) for tasks that fit within the context window
Use a single long-context prompt with structured inputs, or implement native tool use/function calling, rather than chaining separate model calls.
Journey Context:
Prompt chaining was a necessity when context windows were 4k-8k tokens. You had to break tasks down into separate API calls \(summarize, then extract, then format\). With 128k\+ context windows and native tool use, chaining introduces unnecessary latency, state management complexity, and error propagation. A single agentic loop with tools, or a single well-structured prompt, is more robust and allows the model to maintain full context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:45:56.493650+00:00— report_created — created