Skip to content

v0.1.3

Choose a tag to compare

View all tags
@Tyan66666 Tyan66666 released this 14 Aug 07:13
· 15 commits to main since this release
v0.1.3
24b68a9

What's new

compress / resolveSurfaceRange errors now guide the model (commit 958a5b8)

When a range edge is not a real surface node — e.g. seq 9..1500 in a fresh session where surface seqs are sparse — the error now explains why and points the model at acp_status:

billion-context-dsh: seq 999999..999999 not in the current surface — surface seqs
are sparse message nodes (only user/message, assistant/message, tool/result
events); consult acp_status for the current surface range

In acceptance testing (session bb0005ca) the model guessed wrong boundaries twice, read source, self-corrected, and compressed the real range in one shot. This release removes the need to dig into source: the error itself is the hint.

Verified live

  • acp_status online after restart: 6 blocks, 294691 tokens compressed, surface 47 nodes seqs 79280..345792
  • Invalid-range compress probe returned the new guided error verbatim
  • 33/33 tests green, typecheck clean, build OK
Assets 2
Loading