Piper · Coding harness
Log in

Summary / The 27 components

08a Context compaction

Keeping a long session working when its context fills: summarize, trim and continue, instead of truncating or dying.

Latest—not scored
Baseline— 
Live use—last 7 days

Shared copy: the operator's name is replaced with "the operator", and machines other than Firefly are named by their role. Nothing else is changed.

What is built now

Nothing in the harness.

What is missing

A session_before_compact handler (one summarizer prompt plus re-injection of the assembler blocks) and the diagnostic comparing sessions that compacted with those that did not.

Reviewer Claude, 2026-10-04

Reviewer's read: Not started; spec written for another product

The paper transcribed a community reconstruction of Claude Code's compaction layers, which do not exist in pi. The reconciliation reduced it to one handler on pi's own event. There is little pressure to build it: harness sessions are short (a few minutes on most tasks), and the turn and token caps that used to end them have been removed from every control arm.

How it is measured proposed

Fault test that forces a compaction mid-task; then the resolve rate of compacted against uncompacted sessions.

Adoption rules shared by every arm: How the tests work.

Research & attempts

No documents yet.

Score history

No scores yet. The first entry is the baseline for suite v1.

Experimental record

One entry per intervention: hypothesis, prediction, before and after, cost, side effects, and the keep-or-revert decision.

No interventions recorded yet.