You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add commit_cluster_trigger config (enabled: true, min_clusters: 3 by default)
allowing users to tune or disable commit-cluster based historian triggering
- Fix heuristics blocked when ctx_reduce_enabled=false (no pending ops meant
tool cleanup and reasoning clearing never ran on execute passes)
- Update heuristic log message from misleading 'pending_ops_execute' to 'scheduler_execute'
- Fix dashboard cache diagnostics labeling old events as 'First message (new session)'
by checking whether earlier assistant messages exist in the DB
- Add commit cluster trigger toggle + min clusters input to dashboard config editor
- Document commit_cluster_trigger in CONFIGURATION.md with explanation of what
commit clusters are
Copy file name to clipboardExpand all lines: CONFIGURATION.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,6 +49,27 @@ Higher-tier models with longer cache windows benefit from a longer TTL. Setting
49
49
|`compartment_token_budget`|`number`|`20000`| Token budget for historian input chunks. |
50
50
|`historian_timeout_ms`|`number`|`300000`| Timeout per historian call (ms). |
51
51
|`history_budget_percentage`|`number` (0–1) |`0.15`| Fraction of usable context reserved for the history block. Triggers compression when exceeded. |
52
+
|`commit_cluster_trigger`|`object`| See below | Controls the commit-cluster historian trigger. |
53
+
54
+
### `commit_cluster_trigger`
55
+
56
+
A **commit cluster** is a distinct work phase where the agent made one or more git commits, separated from other commit clusters by meaningful user turns. For example, if the agent commits a fix, then the user asks a new question, and the agent commits another change — that's 2 commit clusters. This heuristic detects natural work-unit boundaries and fires historian to compartmentalize them, even when context pressure is low.
57
+
58
+
```jsonc
59
+
{
60
+
"commit_cluster_trigger": {
61
+
"enabled":true, // default: true
62
+
"min_clusters":3// default: 3, minimum: 1
63
+
}
64
+
}
65
+
```
66
+
67
+
| Field | Type | Default | Description |
68
+
|-------|------|---------|-------------|
69
+
|`enabled`|`boolean`|`true`| Enable commit-cluster based historian triggering. |
70
+
|`min_clusters`|`number`|`3`| Minimum number of commit clusters in the unsummarized tail before historian fires. The tail must also contain at least `compartment_token_budget` tokens. |
71
+
72
+
Set `enabled: false` to disable this trigger entirely and rely only on pressure-based and tail-size triggers for historian.
<spanclass="config-field-desc">Fire historian when enough git commit clusters accumulate in the unsummarized conversation tail. A commit cluster is a distinct work phase where the agent made git commits, separated by meaningful user turns.</span>
0 commit comments