A compaction reads as a failure: say it is coming, show it happening, and let the context ring drop after it #185
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Seen on 2026-10-17 in the #172 comparison's single-step run (run_01M55284MNP9F2CE8NK5D3D96A, context per agent 90,000, alarm 67,500).
openspec.apply[all]compacted in place three times, each working: 69k → 9k, 72k → 10k, 73k → 10k. What the console showed did not say so.What is wrong
budget alarm: stp_01M552936MKDZRZYCPJ1MHEGV6, a rule, and theninterrupted(the turn cut at the alarm). The step id means nothing to the operator, "interrupted" sounds like a failure, and nothing says a compaction is under way or what came of it until the "context compacted" line appears.max()of the primary session's turns since the last respawn (src/osf/engine/digest.py,_SESSION_PEAK_SQL). A handoff moves that start to the new session; a compaction in place keeps the same session, so the pre-compaction turn stays in the max.What it should do
osfd transcriptand notifications (osf/format.pyparity).Done when
Also in scope, seen in the same run: the spine's activity line reads "Starting · 6m 23s" (code review) and "Starting · 50m 14s" (the apply step) while the transcript shows the agent thinking. The line derives from durable events only, and a long reasoning stretch persists nothing until it ends, so after an alarm it stays on "Starting". It should say "Thinking" while reasoning streams (stream B's reasoning deltas), and "compacting" during a compaction.
Shipped in
443263a(mergea2a4fd8), live since 19:00Z on 2026-10-17. It was adapted to #186 in86dc37f(20:11Z), and the activity-line fixes went out infdd6c70(23:28Z). Archived in OpenSpec ascompaction-reads-as-progressin874eb27.What shipped
Commits:
c149a13,ca68b1c,16598f7,93c7ac1,d17bd6b,6724257, and after reviewfdb5e65,6b79b1c,d3117d2. The activity line:11fe6c5,54e295f,4a5d36a.Checked on production, on run 74 (
86dc37f, one step at 90,000), at 20:22Z:Not seen on production yet: the same run showed "Starting · 12m 52s" for about 90 s after a compaction. The fix (
11fe6c5, with the follow-ups54e295fand4a5d36a) went out infdd6c70, but nobody has watched a compaction on production since. Half of the change's workflow note, watching a step through a handoff, no longer applies: #186 removed the handoff.Closing. Please reopen if a compaction on
fdd6c70still reads "Starting".