Fix URL-encoded Unicode artifact links - #225
Open
kudala-bharani wants to merge 2 commits into
Open
Conversation
kudala-bharani
marked this pull request as ready for review
July 27, 2026 04:43
kudala-bharani
force-pushed
the
agent/fix-artifact-preview-links
branch
from
August 1, 2026 16:58
2ae3679 to
3739653
Compare
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.
Fixes #223
What changed
Upstream reconciliation
Current
mainnow handles artifact reads across the workspace, scratch directory, and granted roots, while intentionally keeping the Artifacts list scratch-only. This branch was updated to preserve that architecture, and the superseded broad-root scanning changes were dropped.Validation
npm test -- src/components/Markdown.test.tsx— 5 passednpm test— 22 files / 140 tests passednpx tsc --noEmit— passednpm run build— passedThe Playwright browser suite could not complete locally because its Vite test server stopped responding during page navigation; the focused regression passes, and that browser failure occurred before the tested interaction.