[GH-ISSUE #256] feat: per-workspace override for the workspace memory char limit #169

New issue

Open

opened 2026-10-18 14:03:33 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:03:33 +00:00

Owner

Originally created by @1-kabir on GitHub (Sep 5, 2026).
Original GitHub issue: https://github.com/open-webui/computer/issues/256

feat: per-workspace override for the workspace memory char limit

Feature description

The workspace memory character limit is a single global admin setting. Larger
or smaller workspaces may warrant different memory budgets, but the global
value applies everywhere.

Proposed solution

Allow admins to override the workspace memory char limit per workspace from
the Memory settings UI:

Overrides stored as a path-keyed map in the existing config table (e.g. memory.workspace_char_limit_overrides).
Resolved inside get_memory_settings(), so writes, recall budgets, and background review all honor the override with no other changes.
PUT /api/memory/config accepts a workspace and routes the workspace limit into the override map; clearing it falls back to the global value.
Memory settings UI shows a workspace limit input when a workspace is active.
Clamp/validate override values; handle invalid input gracefully.

Additional context

Implemented on a fork, including tests (override resolution, clamping, invalid values, clearing, batch-write enforcement).

Originally created by @1-kabir on GitHub (Sep 5, 2026). Original GitHub issue: https://github.com/open-webui/computer/issues/256 feat: per-workspace override for the workspace memory char limit ### Feature description The workspace memory character limit is a single global admin setting. Larger or smaller workspaces may warrant different memory budgets, but the global value applies everywhere. ### Proposed solution Allow admins to override the workspace memory char limit per workspace from the Memory settings UI: - Overrides stored as a path-keyed map in the existing config table (e.g. `memory.workspace_char_limit_overrides`). - Resolved inside `get_memory_settings()`, so writes, recall budgets, and background review all honor the override with no other changes. - `PUT /api/memory/config` accepts a workspace and routes the workspace limit into the override map; clearing it falls back to the global value. - Memory settings UI shows a workspace limit input when a workspace is active. - Clamp/validate override values; handle invalid input gracefully. ### Additional context Implemented on a fork, including tests (override resolution, clamping, invalid values, clearing, batch-write enforcement). ---

No labels

enhancement

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

open-webui/computer#169

No description provided.

Rows
Columns