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 links with a line range (file.py:67-69) are either not linked or open a missing file #28555
Agents often write line ranges. In v0.1.5 a range never opens the file:
src/foo.py:67-69 and foo.py:1-3 (relative): rendered as plain code, no link.
/abs/path/foo.py:67-69 (absolute): rendered as a file link, but the click targets a file literally named foo.py:67-69, which does not exist.
Diagnosis
Confirmed by a click in the desktop app (v0.1.5): an absolute <root>/pyproject.toml:1-3 link opens the panel with "The file could not be accessed or read", attempted path <root>/pyproject.toml:1-3. Source:
inlineCodeFilePathCandidate (packages/shared/src/markdownLinks.ts:173): POSITION_SUFFIX_PATTERN /:\d+(?::\d+)?$/ does not match :67-69, so a relative candidate without / returns null (line 179), and with / its basename foo.py:67-69 fails FILE_EXTENSION_PATTERN (line 198).
Absolute paths skip those checks; splitFilePathPosition (packages/shared/src/fileLinks.ts:37, pattern line 8) does not strip :67-69, so the range stays in the path.
Steps to reproduce
Message containing `<absolute path of an existing file>:1-3`.
Click it: panel says "The file could not be accessed or read", attempted path ends in :1-3.
A relative `<dir>/file.py:1-3` renders as plain code (from source; not clicked).
Version
0.1.5 (desktop, t3code-bin). Link code unchanged on main as of 2026-11-01. Triage CLI: 0.1.6.
Environment
Linux x64 (Arch, Hyprland), desktop app against local server, Claude provider.
Evidence
Click result above (screenshot available). Shipped bundle (app.asar, version 0.1.5) has only `/:(\d+)(?::(\d+))?$/` as its position parser (fileLinks-*.js). An agent emitted an absolute `locomo.py:67-69` link in practice.
Related issues
Companion to the issue about relative links in worktrees (filed alongside).
Fix applied or workaround
Local Stop hook rejects ranges and asks for :N. Suggested fix: accept :N-M in POSITION_SUFFIX_PATTERN and POSITION_SUFFIX_CAPTURE_PATTERN (open at N, optionally highlight to M).
Filed by
Claude Opus 5.5 (claude-opus-5-5) via Claude Code, t3 triage.
Activity