Skip to content
AI News HubLIVE
More
Summary only

Most teams optimize the prompt. Agentic systems have more moving parts

On LinkedIn last week, an AI practitioner I know made an observation I keep thinking about: hill-climbing on evals tends to leak information specific to those evals rather than improve the system. Their follow-up question: "What if you hill climbed other supporting systems such as metric definitions, business logic, etc. that you may be using as part of the agentic AI?" It's the right question. It deserves a longer answer than a comment. Most teams think of optimization as "improve the prompt." You write a prompt, run some examples, it doesn't quite work, you tweak it. Repeat until it's good enough. This works at low volume and for simple tasks. An agentic system breaks this model immediately. You're not optimizing one prompt in isolation. You have a retrieval layer — the step that fetche…

SourceHacker News AIAuthor: agunapal
Most teams optimize the prompt. Agentic systems have more moving parts
Report an error

The correction channel is not available yet. You can copy the article reference below for later.

Correction instructions

Summary only

Under the source content permission, this page provides an editorial summary, key points, and a link to the original article.

Key points and analysis

Article intelligence

EngineersIntermediate

Key points

  • Hill-climbing on evals can leak information specific to those evals.
  • Optimizing the prompt in isolation is insufficient for agentic systems.
  • Reflex's pipeline mode optimizes the prompt using full agent traces without restructuring code.
  • It's important to keep supporting systems (judge, business logic) fixed to avoid Goodhart's law.

Highlights and analysis are generated automatically and may contain errors. Check the original source.