You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: wire up memory injection into system prompt with telemetry
- Inject memory blocks into system prompt at session start, gated by
ALTIMATE_DISABLE_MEMORY flag
- Add memory_operation and memory_injection telemetry events to App Insights
- Add memory tool categorization for telemetry
- Document disabling memory for benchmarks/CI
- Add injection integration tests and telemetry event tests
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/docs/data-engineering/tools/memory-tools.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,16 +132,27 @@ Files are human-readable and editable. You can create, edit, or delete them manu
132
132
133
133
Blocks are written to a temporary file first, then atomically renamed. This prevents corruption if the process is interrupted mid-write.
134
134
135
+
## Disabling memory
136
+
137
+
Set the environment variable to disable all memory functionality — tools and automatic injection:
138
+
139
+
```bash
140
+
ALTIMATE_DISABLE_MEMORY=true
141
+
```
142
+
143
+
This is useful for **benchmarks**, CI pipelines, or any environment where persistent memory should not influence agent behavior. When disabled, memory tools are removed from the tool registry and no memory blocks are injected into the system prompt.
144
+
135
145
## Context window impact
136
146
137
-
Altimate Memory injects relevant blocks into the system prompt at session start, subject to a configurable token budget (default: 8,000 characters). Blocks are sorted by last-updated timestamp, so the most recently relevant information is loaded first.
147
+
Altimate Memory automatically injects relevant blocks into the system prompt at session start, subject to a configurable token budget (default: 8,000 characters). Blocks are sorted by last-updated timestamp, so the most recently relevant information is loaded first. The agent also has access to memory tools (`altimate_memory_read`, `altimate_memory_write`, `altimate_memory_delete`) to manage blocks on demand during a session.
138
148
139
149
**What this means in practice:**
140
150
141
151
- With a typical block size of 200-500 characters, the default budget comfortably fits 15-40 blocks
142
152
- Memory injection adds a one-time cost at session start — it does not grow during the session
143
153
- If you notice context pressure, reduce the number of blocks or keep them concise
144
154
- The agent's own tool calls and responses consume far more context than memory blocks
155
+
- To disable injection entirely (e.g., for benchmarks), set `ALTIMATE_DISABLE_MEMORY=true`
145
156
146
157
!!! tip
147
158
Keep blocks concise and focused. A block titled "warehouse-config" with 5 bullet points is better than a wall of text. The agent can always call `altimate_memory_read` to fetch specific blocks on demand.
0 commit comments