feat(agent): persist and report context usage#239
Merged
Conversation
jiahe0510
force-pushed
the
jiahe/feat/context-usage
branch
from
July 23, 2026 09:27
af55592 to
b3c78a6
Compare
jiahe0510
marked this pull request as ready for review
July 23, 2026 10:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
context_statein sessionstate.json, including current context usage, usage source, compact/microcompact counts, and update time./contextand/context allwith category estimates, and exposeAgentEngine::context_status()for SDK hosts.Why
AionCore needs aionrs to own the effective context window and compaction decisions. Previously, the current context watermark and compaction history were runtime-only, so restarts lost that status and hosts could not query a consistent context view.
Non-goals
Validation
just push -u origin jiahe/feat/context-usagecargo fix --allow-dirty --allow-stagedcargo clippy --fix --workspace --all-targets --allow-dirty --allow-staged -- -D warningscargo fmt --allcargo nextest run --workspace --profile defaultcargo hakari generate --diffcargo hakari manage-deps --dry-runcargo hakari verifycargo test -p aion-agentcargo check --workspacegit diff --checkFollow-up
After this lands and is released, AionCore can consume
AgentEngine::context_status()and emit a structured context-status event for AionUi.