Skip to content

v0.12.1 — Capped Threshold Readout in /context tune

Choose a tag to compare

@DusanCar-sudo DusanCar-sudo released this 26 Jul 13:22
· 120 commits to master since this release

Highlights in v0.12.1

Patch release over v0.12.0.

  • /context tune now reports the threshold compaction actually uses. The tuner showed each rung as a plain share of the context window, ignoring the absolute context.maxTokens cap. On a 1M-window model it claimed compaction fires at 550.0k while the engine fired at the 80k cap — so on exactly the models the cap was introduced for, the tuner was reporting a number nothing in the system used.
  • Rungs held at the cap are marked, and a fully inert ladder says so. Previously, moving a rung that sat entirely above the cap changed the display but could not change behaviour, with nothing on screen explaining why.
  • /ct — short alias for /context tune, in :help and the README.

Before:

  ◆ Context: ████░░░░░░░┊░░┊░░┊░░ 21% (210.0k/1000k)
                        ▲  rung 1/3: 55% (550.0k)

After:

  ◆ Context: ████░░░░░░░┊░░┊░░┊░░ 21% (210.0k/1000k)
                        ▲  rung 1/3: 55% (80.0k — capped)
  ladder: 55% → 70% → 85%
  ladder inert: every rung is above the 80k cap — raise context.maxTokens

The bar geometry is unchanged — rungs still plot at their window share, keeping the tuner consistent with the context footer.

Full detail in CHANGELOG.md.

npm install -g aura-code@0.12.1