Report #38700
[architecture] Putting all agent instructions and user facts in the static system prompt
Use a mutable Core Memory block \(in-context\) that the agent can explicitly edit via tool calls \(insert/delete\), keeping it strictly bounded in size, and push everything else to Archival Memory.
Journey Context:
System prompts are static. If an agent learns a new user preference \(e.g., 'User prefers tab size 2'\), it cannot update the system prompt for the next turn. By giving the agent a mutable Core Memory \(a structured text block it can rewrite\), the agent can actively learn and adapt its own working context without exceeding token limits.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T19:26:10.761569+00:00— report_created — created