[GH-ISSUE #114] bug: Per-model compression threshold not reflected in status display #53

New issue

Closed

opened 2026-10-18 14:02:25 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-18 14:02:25 +00:00

Owner

Originally created by @JKGeovision on GitHub (Jul 8, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/114

Hello,

I discovered a bug where the per-model compression threshold does not display correctly in the status window, even when properly configured.

Steps to reproduce:

Go to Settings and set a global compression trigger (e.g., default 80k)
Navigate to a specific model's settings and set a per-model compression threshold (e.g., 250k)
Observe the status window when using that model
The status displays the global threshold instead of the per-model threshold (e.g., shows "4.8k/80k" instead of "4.8k/250k")

I suspect the status display is hardcoded to read from the global compression trigger setting rather than checking for a per-model override.
I haven't tested whether this affects the actual compression trigger behavior or if it's only a UI display error. The per-model threshold may still be applied correctly in the background despite the incorrect display.

Thank you for your work and I wish you all a great day,
Joshua Krimmer

Originally created by @JKGeovision on GitHub (Jul 8, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/114 Hello, I discovered a bug where the per-model compression threshold does not display correctly in the status window, even when properly configured. Steps to reproduce: 1. Go to Settings and set a global compression trigger (e.g., default 80k) 2. Navigate to a specific model's settings and set a per-model compression threshold (e.g., 250k) 3. Observe the status window when using that model 4. The status displays the global threshold instead of the per-model threshold (e.g., shows "4.8k/80k" instead of "4.8k/250k") I suspect the status display is hardcoded to read from the global compression trigger setting rather than checking for a per-model override. I haven't tested whether this affects the actual compression trigger behavior or if it's only a UI display error. The per-model threshold may still be applied correctly in the background despite the incorrect display. Thank you for your work and I wish you all a great day, Joshua Krimmer

bsakaguchi closed this issue

2026-10-18 14:02:25 +00:00

bsakaguchi commented

2026-10-18 14:02:26 +00:00

Author

Owner

@tjbck commented on GitHub (Jul 9, 2026):

Should be addressed!

@tjbck commented on GitHub (Jul 9, 2026): Should be addressed!

bsakaguchi referenced this issue

2026-10-18 14:04:15 +00:00

[PR #53] [MERGED] 0.4.8 #264