Skip to content

blog: Stop Growing Your System Prompt - #4099

Draft
benfrank241 wants to merge 1 commit into
mainfrom
blog/stop-growing-system-prompt
Draft

blog: Stop Growing Your System Prompt#4099
benfrank241 wants to merge 1 commit into
mainfrom
blog/stop-growing-system-prompt

Conversation

@benfrank241

Copy link
Copy Markdown
Member

Argues that the default fix for an agent that forgets — adding another line to the system prompt — has a structural ceiling.

Opens by conceding what the prompt is good at: immediate, certain to be seen, inspectable. A strawman would be easy to dismiss.

Then the costs:

  • Paid on every turn regardless of the task
  • Crowds out the work itself
  • Relevance falls as size grows, so adding a rule can make an existing rule less likely to be followed — maddening to debug, because the line you added is fine and the line that broke is untouched
  • It only ever grows, because adding is cheap and deleting requires knowing a line is obsolete

The distinction it turns on: instructions vs knowledge. Instructions are unconditional and belong in the prompt. Knowledge is unbounded and mostly irrelevant to the current task, so putting it in the prompt means paying for all of it to get any of it. Uses the documented recall budget defaults (fixed: low 100, mid 300, high 1000 per method per fact type; plus adaptive) to make the per-request alternative concrete.

Closes on honest limits: retrieval can miss, adds a dependency, and needs time before it beats a well-written prompt. "For a script you'll run twice, put it in the prompt."

Composite 87.8/100, specificity 100, readability 94. All cross-links verified live.

Draft — for review, not merge.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AE4NCnCKXUzNDF3N9FaQja

Argues that the default fix for an agent that forgets, adding another line
to the system prompt, has a structural ceiling.

Opens by conceding what the prompt is genuinely good at: it is immediate,
certain to be seen, and inspectable. Then the costs. The prompt is paid on
every turn regardless of the task, it crowds out the work itself, and
relevance falls as size grows, so adding a rule can make an existing rule
less likely to be followed. It also only ever grows, because adding is
cheap and deleting requires knowing a line is obsolete.

The distinction the post turns on is instructions versus knowledge.
Instructions are unconditional and belong in the prompt. Knowledge is
unbounded, mostly irrelevant to the current task, and belongs somewhere
retrievable, where the cost is per-request rather than permanent. Uses the
documented recall budget defaults to make that concrete.

Closes on the honest limits: retrieval can miss, adds a dependency, and
needs time before it beats a well-written prompt.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AE4NCnCKXUzNDF3N9FaQja
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant