Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -424,13 +424,13 @@ The default configuration (what `GET /config` returns out of the box):
"min_tokens_to_compress": 250,
"kompress_model": null,
"savings_profile": null,
"headroom_version": "0.30.0"
"headroom_version": "0.31.0"
}
```

`headroom_version` is read-only — the headroom-ai version tsheadroom detected on its workers (omitted until the first worker reports ready). It's informational and reflects which knobs the running headroom can actually honor.

The tunable surface below tracks headroom-ai's library `compress()` API, which is intentionally stable: 0.27.0 through 0.30.0 added no new `CompressConfig` knobs, so the fields here are unchanged since 0.26.0 (which introduced `savings_profile`). The one profile-surface change is that 0.30.0 added the `coding` and `general` presets alongside `agent-90` and `balanced`. Newer headroom releases still improve the compression that runs *inside* `compress()` — you get those automatically with no config change. The extra power those releases added (e.g. `force_kompress`, `--protect-tool-results`) lives in headroom's proxy pipeline, which `compress()` does not expose.
The tunable surface below tracks headroom-ai's library `compress()` API, which is intentionally stable: 0.27.0 through 0.31.0 added no new `CompressConfig` knobs, so the fields here are unchanged since 0.26.0 (which introduced `savings_profile`). The one profile-surface change is that 0.30.0 added the `coding` and `general` presets alongside `agent-90` and `balanced`. Newer headroom releases still improve the compression that runs *inside* `compress()` — you get those automatically with no config change. The extra power those releases added (e.g. `force_kompress`, `--protect-tool-results`) lives in headroom's proxy pipeline, which `compress()` does not expose.

Changes take effect on the next request. Invalid values are rejected with `400` and leave the current configuration untouched (for example, `target_ratio: 5` → `target_ratio must be in (0, 1] or null`; `savings_profile: "fast"` → `savings_profile must be one of agent-90, balanced, coding, general, or null`). You can also edit the `-config` JSON file directly and restart.

Expand Down
Loading