Repository navigation
fix(configurator): share configuration chats within workspaces - #286
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
November 20, 2026 17:35
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Saved configurations currently have separate personal Assistant histories, and browser state can outlive a workspace/configuration switch. Authorized Platform Engineers will now read and continue one conversation per saved configuration, with message authors and revision checks that prevent concurrent replies from overwriting newer history.
Migration 102 preserves existing personal histories under their original owner policies. The author can explicitly copy one into an empty shared conversation; histories are never automatically merged or exposed. New configuration context is shared with the configuration. A participant change rebuilds the private consultation brief from shared history with the current participant’s identity and permissions. Acceptance, saving and cloud execution remain separate.
The browser aborts requests and resets chat state when scope changes, sends explicit workspace headers, and polls for team updates while preserving unsent input. English/German product guidance and source-bound Assistant knowledge are updated. Curated v2.2.3 notes are included.
Validation: 59 PostgreSQL integration tests; 12 desktop/mobile browser checks covering configuration switching, author display, teammate refresh, discard, template consultation, firewall merge and explicit proposal acceptance; targeted real-model shared-chat advice passed twice independently. Full application lint/build/tests pass: 2,181 tests passed and 100 environment-dependent tests skipped; the separate PostgreSQL run passes all 59 tests. Nine release-lifecycle checks also pass. These targeted tests do not close the wider Assistant qualification limitations in #275; release mode remains
skip.Closes #285.
The runner-recovery/MailOut foundation has passed Dev deployment in run 44780529409. A new immutable build will combine it with this chat fix for Dev and the subsequent v2.2.3 production promotion. Production publication remains blocked pending explicit approval of the required SMTP-secret transfer. No customer State or cloud resources are changed by sharing or continuing a chat.