Capture only settled, correctly sized browser screenshots - #321
Merged
hamzamerzic merged 2 commits intoJul 28, 2026
Conversation
Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
Co-authored-by: Möbius Agent <mobius-agent@users.noreply.github.com>
This was referenced Jul 28, 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.
Problem
Authenticated screenshot automation could report success while keeping the wrong visual frame. Browser commands could split across daemon identities, navigation could replace the page after viewport setup, and DOM readiness could precede the compositor's useful paint. Shell handoffs also retain fully laid-out chat surfaces during opacity and mode transitions. A retained Chromium profile could additionally stay locked to a process from a previous container, preventing cold capture entirely.
Fix
Prior work
PR #59 hardened final-boundary screenshot authentication. PR #304 integrated the cold-start and freshness foundation. This follow-up preserves those contracts while closing the remaining daemon, final-viewport, shell-ownership, compositor, and retained-profile races exposed by live captures.
Verification