@ai-agent-forge/agent-forge 0.85.5 → 0.85.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +7 -1
- package/dist/bundle/.build-manifest.json +6 -6
- package/dist/bundle/chunks/{chunk-7YVQMWO5.js → chunk-WD7FTOHY.js} +2 -2
- package/dist/bundle/cli.js +1 -1
- package/dist/bundle/index.js +1 -1
- package/dist/bundle/rpc-entry.js +1 -1
- package/dist/core/agent-session-compaction.d.ts.map +1 -1
- package/dist/core/agent-session-compaction.js +6 -0
- package/dist/core/agent-session-compaction.js.map +1 -1
- package/dist/core/agent-session.d.ts +4 -0
- package/dist/core/agent-session.d.ts.map +1 -1
- package/dist/core/agent-session.js.map +1 -1
- package/dist/modes/interactive/interactive-mode.d.ts.map +1 -1
- package/dist/modes/interactive/interactive-mode.js +5 -0
- package/dist/modes/interactive/interactive-mode.js.map +1 -1
- package/docs/compaction.md +2 -0
- package/package.json +1 -1
package/docs/compaction.md
CHANGED
|
@@ -35,6 +35,8 @@ By default, `reserveTokens` is 16384 tokens (configurable in `~/.agent-forge/age
|
|
|
35
35
|
|
|
36
36
|
During a multi-turn agent run, Pi checks this threshold after tools finish and their results are appended, before starting the next assistant response. If the threshold is crossed, Pi compacts inside the same agent run and resumes with the summary and retained messages. It skips this between-turn check when the completed tool batch terminates the run and no queued message requires another response. Pi also checks the threshold before a new user prompt and after a low-level agent run ends.
|
|
37
37
|
|
|
38
|
+
When the threshold is crossed but the entire session history falls inside the `keepRecentTokens` budget, there is no summarizable prefix and auto-compaction skips without a `compaction_start`. The session emits a `compaction_skipped` event (with the trigger `reason` and `cause: "nothing_to_compact"`) so hosts can surface the "context is full but nothing compacts" state; the interactive TUI shows it as a transient status line. Manual `/compact` reports the same condition as the "Nothing to compact (session too small)" error.
|
|
39
|
+
|
|
38
40
|
You can also trigger manually with `/compact [instructions]`, where optional instructions focus the summary.
|
|
39
41
|
|
|
40
42
|
### How It Works
|