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
main.tsx defaultNotFound component is being rendered instead a root pathless route notFoundComponent #6351
Click on the Skill Agent button in the home page, You will be redirected to skill-agent page
Now manually go the the route to trigger not-found component http://localhost:3000/agents/skill-agen
The not-found component in the _authenticated/agents/route.tsx will be triggered (Which is expected)
Now go the location in the codebase _authenticated/agents/route.tsx and comment the notFoundComponent
Now navigate to the same link http://localhost:3000/agents/skill-age the main.tsx defaultNotFoundComponent is being triggered instead of _authenticated.tsxnotFound component
Expected behavior
For root pathless route (say routes/_authenticated.tsx) the notFound component is not being triggered and main.tsxdefaultNotFoundComponent is being triggered. I didn't change the default behaviour of notFoundMode (which is fuzzy)
This appears to be the same issue as #4065, which was reported back in April 2025 — over 8 months ago. It seems like the notFoundComponent on pathless layout routes has been broken for quite a while now. Is there any update on when this might be addressed? Many users seem to be affected by this.
Activity
rahulvils commentedon Jan 10, 2026
You can see the video here - https://github.com/rahulvils/tanstack-router-not-found/blob/main/public/issue.mp4
missish commentedon Jan 14, 2026
This appears to be the same issue as #4065, which was reported back in April 2025 — over 8 months ago. It seems like the
notFoundComponenton pathless layout routes has been broken for quite a while now. Is there any update on when this might be addressed? Many users seem to be affected by this.rahulxdemon commentedon Jan 14, 2026
This is the latest version and I still have not resolved
rahulxdemon commentedon Aug 5, 2026
This issue is fixed :)