You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
File preview: root-relative markdown images (/images/…) render as missing #23623
I searched open issues and this is not already reported.
KiroCrew version
0.9.0.4
Release channel
Not sure
How is it installed?
Desktop app
Platform
Not platform-specific
What happened
A markdown file opened in the file preview shows every image written as a root-relative path () as a broken-image chip reading "Image file no longer exists", although the files are on disk.
/images/… is the conventional way to reference an image from the root of the repository or site the markdown belongs to. GitHub renders a root-relative image in a README against the repository root, and Zenn, Docusaurus and similar static-site setups write images the same way. The preview instead reads the path as an absolute filesystem path (/images/… at the root of the disk), so /api/file-raw answers 404, and the HEAD probe turns that into the "no longer exists" wording.
Expected: when the absolute path does not exist and the image sits in a file preview (a BasePathCtx is set), the preview also tries the path against the directories above the markdown file, nearest first, and shows the first one that loads. A path that really is absolute (/Users/…/shot.png) keeps working on the first request.
The cause is in website/src/components/markdown/ImgWithFallback.tsx: the basePath branch resolves only paths that do not start with /, ~ or a drive letter, so a leading-slash path is sent to /api/file-raw verbatim.
Steps to reproduce
Create repo/articles/post.md containing  and put an image at repo/images/post/shot.png.
Open repo/articles/post.md in the dashboard's file preview.
The image renders as a broken-image chip, "Image file no longer exists".
Anything else
Workaround today: rewrite the link relative to the file (../images/post/shot.png). That breaks the image on the site the markdown is published to, so it is not a real fix for the file's author.
Related but separate: #10197 (Obsidian ![[…]] embeds in the Notes app) and #4084 (relative images in the Notes app).
Activity
fix(markdown): resolve root-relative images against the file's site root
KiroCrewCaptain commentedon Oct 24, 2026
Thanks for the report. This issue has been triaged by Crew Captain and will be assigned to a maintainer, who will follow up here.
fix(markdown): resolve root-relative images against the file's site root
fix(markdown): resolve root-relative images against the file's site root
inariku commentedon Oct 24, 2026
/claim
Fix is up in #23631.
fix(markdown): resolve root-relative images against the file's site root
KiroCrewCaptain commentedon Oct 24, 2026
@inariku, this issue cannot be claimed right now: someone is already working on it.
fix(markdown): resolve root-relative images against the file's site root
fix(markdown): resolve root-relative images against the file's site root
fix(markdown): resolve root-relative images against the file's site root
fix(markdown): resolve root-relative images against the file's site root
fix(markdown): resolve root-relative images against the file's site root
fix(markdown): resolve root-relative images against the file's site r…