Interface: WindowStrategyResult

Defined in: src/core/agent/window/strategy.ts:127

What the stage should do next.

Properties

budgetPressure?

readonly optional budgetPressure?: object

Defined in: src/core/agent/window/strategy.ts:175

The budget reading to report on agentfootprint.context.budget_pressure.

OMIT IT when the strategy has no token budget. slidingWindow does: it triggers on turn count, and filling capTokens with a number nobody configured would be the invented figure this family refuses. No budget, no budget_pressure event.

unit says what the two numbers count, because the context SLOTS emit this same event name with the same slot: 'messages' and count in CHARS. It defaults to 'tokens' — every shipped strategy compares against a thresholdTokens, so that is what all three already mean. Set it to 'chars' if yours measures characters, and the event will say so.

capTokens

readonly capTokens: number

planAction

readonly planAction: "evict" | "summarize" | "none"

projectedTokens

readonly projectedTokens: number

unit?

readonly optional unit?: "chars" | "tokens"

evictions

readonly evictions: readonly WindowEviction[]

Defined in: src/core/agent/window/strategy.ts:145

Messages that left the window, for context.evicted.

folded?

readonly optional folded?: readonly FoldedSpan[]

Defined in: src/core/agent/window/strategy.ts:160

Spans this visit removed, in the form that OUTLIVES the process: appended to the conversation checkpoint, so a restart can still say what a summary stands for — and, under retain: 'conversation', produce it verbatim.

OMIT IT unless your strategy replaced messages with something that stands for them. summarizeOldest fills it because a summary is a claim that needs its evidence; the drop strategies do not, because a drop replaces nothing and its authored notice claims nothing.

The stage writes these in the SAME commit as the window change, so there is no state in which messages left the window and the record of what they were did not follow them.

rebase?

readonly optional rebase?: object

Defined in: src/core/agent/window/strategy.ts:137

How the meter must re-align its provenance to the new window, which is [...head, (one new message)?, ...tail]. Present exactly when window is. insertedAtMs is the birth of the message the strategy put in the span's place — omit it when the strategy removed messages and inserted nothing.