[felixlaga]

Problem

In a chat message, inline code that names a relative path ending in a well-known extensionless file stays plain code. Examples: docker/Dockerfile, src/Makefile, docs/README. The same file does become a file chip as ./docker/Dockerfile, as an absolute path, as docker/Dockerfile:3, or as a Markdown link.

inlineCodeFilePathCandidate requires a file extension when there is no line number. It does not check EXTENSIONLESS_FILE_NAMES, the list the Markdown link checks in the same module already use.

Change

The inline-code check now also accepts a basename that is in EXTENSIONLESS_FILE_NAMES. Branch names and model ids such as origin/main and z-ai/glm-5.3 stay plain code.

Scope and approval

This is a very small fix for an obvious inconsistency inside one function: the module already treats these names as files everywhere else. It affects every client that renders file chips from inline code: web and desktop (apps/web/src/markdown-links.ts), mobile (apps/mobile/src/lib/markdownLinks.ts) and thread find (packages/shared/src/threadFindText.ts). I searched issues and PRs for "Dockerfile chip", "Makefile chip", "extensionless", "EXTENSIONLESS_FILE_NAMES" and "file chip without extension". #23203 and #22181 touch the nearby line, but they cover extensionless names with a line number, which is a different case.

Verification

• New row ["docker/Dockerfile", "docker/Dockerfile"] in the existing table distinguishes file paths from code and hostnames in %s in packages/shared/src/markdownLinks.test.ts.
• vp test run packages/shared/src/markdownLinks.test.ts with the fix: 55 passed.
• With only markdownLinks.ts reverted to main: AssertionError: expected null to be 'docker/Dockerfile'.
• The web and mobile link tests and the thread-find tests pass. vp run check:changed passes.

Not checked: before/after screenshots in a running client.

Written by Claude Opus 5.5 (claude-opus-5-5) in the Claude Code harness, run from T3 Code.

🤖 Generated with Claude Code

[macroscopeapp]

Approvability

Verdict: Approved at 95db8f4

Macroscope's review found this PR approvable — Inline paths such as docker/Dockerfile now render as file chips using the existing recognized-filename list. The change is limited to path recognition and associated presentation/search behavior, with existing link-resolution safeguards unchanged.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The shared candidate check now accepts configured extensionless basenames without a position suffix. The mobile inline-link pattern now recognizes nested paths ending in configured extensionless filenames.

Changes: Extensionless File Links

Layer / File(s)	Summary
Accept configured extensionless basenames packages/shared/src/markdownLinks.ts, packages/shared/src/markdownLinks.test.ts	The shared candidate check accepts basenames in EXTENSIONLESS_FILE_NAMES when no position suffix is present. The set is exported as a read-only set, and a test covers docker/Dockerfile.
Match nested extensionless file paths apps/mobile/src/lib/enrichedLinkPresentation.ts, apps/mobile/src/lib/enrichedLinkPresentation.test.ts, apps/mobile/src/lib/markdownInlineFileLinks.test.ts	The mobile inline-link pattern uses EXTENSIONLESS_FILE_NAMES to match nested paths with optional line or line-range suffixes. Tests cover docker/Dockerfile and reject Dockerfile and docker/Dockerfiles.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested reviewers: t3dotgg, flamboh

Merge Risk: Minimal · up to 72088

Inline code such as docker/Dockerfile now becomes a file link on both shared and mobile surfaces. Branch names and model IDs stay as plain code. No merge-blocking risk was found.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the main change: inline code paths such as docker/Dockerfile now become file chips. It matches the changeset, which accepts extensionless basenames from EXTENSIONLESS_FILE_NAMES in inl…
Description check		The description follows the template sections: Problem, Change, Scope and approval (in place of Scope), and Verification. It states the bug, the code path, and the fix. It names the affected clients a…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: inline code paths such as docker/Dockerfile now become file chips. It matches the changeset, which accepts extensionless basenames from EXTENSIONLESS_FILE_NAMES in inlineCodeFilePathCandidate, and the objectives describe the same change. It is 73 characters, a single sentence, and uses the conventional commit form.

Full details: Description check

Explanation

The description follows the template sections: Problem, Change, Scope and approval (in place of Scope), and Verification. It states the bug, the code path, and the fix. It names the affected clients and the tests run, and it gives the test row and the revert result. It cites related issues and PRs for the scope check. It omits a link to a specific bug report issue; the author says none is needed for a small obvious fix, and this matches the template's guidance. The Verification section notes that screenshots were not taken, and the change is not a UI change in the visual sense, so that gap is minor. The template asks for the model and harness at the end, and the author lists Claude Opus 5.5 and the Claude Code harness, so that item is present.

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Recent review info

Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 5ee4fd4
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: ee55fb4a-a1bb-4792-9f98-374e13c7ecc4

Commits

Reviewing files that changed from the base of the PR and between 8a00711 and 720881e.

Files selected for processing: 4

• apps/mobile/src/lib/enrichedLinkPresentation.test.ts
• apps/mobile/src/lib/enrichedLinkPresentation.ts
• apps/mobile/src/lib/markdownInlineFileLinks.test.ts
• packages/shared/src/markdownLinks.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

[maria-rcks]

Note

Written by claude-opus-5-5 on behalf of Maria

Merged current main (no rebase) to clear the conflict in packages/shared/src/markdownLinks.ts. Main (#32403) restructured the no-extension branch to handle :line suffixes, so the extensionless-name check now sits inside it: with no position suffix, a basename like Dockerfile returns the candidate, anything else stays plain code. The :line path is unchanged. vp run check:changed passes, including the 74 markdownLinks tests with the docker/Dockerfile row.

[juliusmarminge]

Evidence

Seed the same synthetic project and Replay reply on each commit with all ten reported inline-code examples. Open the reply in web, native iOS, and Electron. In web, also find Dockerfile within the thread and search threads for Dockerfile.

The three bare paths docker/Dockerfile, src/Makefile, and docs/README are plain code before and file chips after on all three clients. Both web and iOS scenarios failed on base and passed on head. Thread find retains three Dockerfile matches; thread search returns the seeded thread. On iOS, z-ai/glm-5.3 already renders as a chip on both commits; origin/main stays plain code.

Surface	Before	After
Commit	5ee4fd4f25	720881e10e
Web, 1280×800
Thread find
Thread search
Native iOS, 402×874
Linux Electron, 1280×900

Sources: web scenario, iOS scenario, Electron driver, runner timeout adjustment.

Not shown:

• Android was not run separately; native mobile evidence covers iOS and the shared mobile rendering path.