Repository navigation
Batch CPU snapshot views to avoid repeated renderer setup - #311
Merged
Merged
Conversation
ksbharaj
approved these changes
Oct 15, 2026
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.
KCL execution snapshots call
session.snapshots()once per view, repeating CPU renderer setup and teardown. Batch views that share a zoom setting so a typical multi-view request uses one call. Mixed named and custom views keep their default zoom behavior in separate batches, with images and completed view names restored to request order.Retry failed or incomplete batches one view at a time to preserve per-view errors and partial results. Cancellation still propagates without retries. Bump the MCP package and registry manifest to
0.28.12.Addresses the snapshot batching comment on #310.