Skip to content

Link inline code file paths in chat markdown - #4726

Merged
juliusmarminge merged 7 commits into
mainfrom
t3code/link-inline-code-filepaths
Jul 28, 2026
Merged

juliusmarminge merged 7 commits into
mainfrom
t3code/link-inline-code-filepaths

fix(web): broaden posix roots for absolute inline paths

c09f076
Select commit
Loading
Failed to load commit list.
MacroscopeApp / Macroscope - Effect Service Conventions succeeded Jul 28, 2026 in 16s

Effect Service Conventions: No findings

All clear

Details

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.

The changed files (apps/web/src/components/ChatMarkdown.tsx, apps/web/src/components/chat/SkillInlineText.tsx, apps/web/src/markdown-links.ts, and apps/web/src/markdown-links.test.ts) concern markdown rendering and pure file-link resolution helpers. They do not create, move, refactor, or consume any Effect service, and contain no Effect module imports, Context.Service tags, layers, error classes, or runtime boundaries. The Effect service conventions therefore do not apply, and there are no violations to report.


🔍 Agent activity — reasoning, no tool calls

💭 Looking at this PR, it's modifying markdown link handling in React components — specifically how links are resolved in markdown files. The Effect service check doesn't apply here since there's no Effect service code being created or consumed, just pure functions and React components for markdown rendering. I need to output JSON per the schema, so I'll respond with a success state confirming there are no Effect service findings to report.


Agent Credits: 22 credits