Conversation
This branch has not been deployed
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.
Problem
GET /notificationscurrently callsservice.snapshot(), which loads tasks, goals, monitors, ideas, memories, artifacts, notifications, identity, and worker state only to return the notifications array.With retained terminal tasks, that makes notification polling scale with the entire workspace.
A downstream PGlite benchmark with 2,000 task rows measured roughly:
Change
Read
notificationsdirectly from the Store. Payload shape and ordering stay the same as the existingdb.listused by the snapshot.Regression
The API test stubs
AgentService.snapshot()to throw and provesGET /notificationsstill succeeds. This fails on the old route and passes with the scoped read.No notification mutation, ownership, or UI behavior changes.