Repository navigation
fix: restore scheduling in personal web chat - #449
Merged
Merged
Conversation
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.
Related to #400.
What Problem This Solves
Fixes an issue where employees could not schedule reminders or recurring tasks from their own private PlatformClaw web conversation.
Why This Change Was Made
Control verifies that the employee's personal Agent owns the conversation. Gateway uses that scope to offer the add-only Automations tool and keeps the Gateway-owner tool restriction for the run. The scheduler verifies signed Agent and session ownership, delivers to the original conversation transcript, and keeps that destination across browser edits.
User Impact
Employees can schedule a reminder or recurring Agent task from their personal web chat and manage the job in Automations. The conversation receives the result. Other Agents, Spaces, and Talk keep their existing authorization boundaries.
Evidence