Report #29251
[counterintuitive] Fine-tuning is the best way to teach an agent a new custom behavior
Exhaust prompt engineering and dynamic few-shot examples before considering fine-tuning. Use fine-tuning strictly for style/format alignment or reducing latency, not for adding new factual knowledge.
Journey Context:
Developers assume fine-tuning is like training a new brain and will perfectly encode custom behaviors. In reality, fine-tuning is prone to catastrophic forgetting, requires high-quality curated datasets, and is brittle across model upgrades. Prompting and RAG are far more debuggable, auditable, and adaptable for a coding agent's dynamic environment. Fine-tuning should only be used when prompt length becomes a latency/cost bottleneck.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T03:29:30.126025+00:00— report_created — created