Disable file pills

[hopperelec]

Whenever a response contains a path-like string enclosed in backticks (e.g., /src/index.ts), T3 Code replaces the backticks with a pill to open that file. However, it does this even if the file doesn't exist, such as if it was never intended to be a file in the first place. For my work, I am finding responses to use this pattern much more often for referencing API paths (e.g., /api/v1/health). To make matters worse, it usually only shows the last path segment (e.g., health), meaning I need to hover over it to see the full context. I never open files from within the T3 Code UI anyway, so this functionality is not helpful for me. Is there a way to disable these file pills entirely?

[charles-benedito]

Looking at the source, there's no setting for this. Inline code becomes a file pill based on the text alone, and nothing checks that the file exists. Anything starting with / counts as a path, which is why /api/v1/health gets picked up:

t3code/packages/shared/src/markdownLinks.ts

Lines 165 to 190 in a71a6c3

	export function inlineCodeFilePathCandidate(codeText: string): string | null {
	const trimmed = codeText.trim();
	if (trimmed.length === 0 || INLINE_CODE_DISQUALIFIER_PATTERN.test(trimmed)) return null;
	const candidate = isWindowsAbsolutePath(trimmed) ? trimmed : trimmed.replaceAll("\\", "/");
	const hasPosition = POSITION_SUFFIX_PATTERN.test(candidate);
	if (!hasPosition && !PATH_SEPARATOR_PATTERN.test(candidate)) return null;
	const hasExplicitPathShape =
	RELATIVE_PATH_PREFIX_PATTERN.test(candidate) ||
	candidate.startsWith("/") ||
	isWindowsAbsolutePath(candidate);
	if (!hasExplicitPathShape) {
	const withoutPosition = candidate.replace(POSITION_SUFFIX_PATTERN, "");
	const firstSegment = withoutPosition.split("/")[0] ?? withoutPosition;
	if (looksLikeHostname(firstSegment, hasPosition)) return null;
	const basename =
	withoutPosition
	.replace(/[/\\]+$/, "")
	.split(/[\\/]/)
	.at(-1) ?? "";
	if (VERSION_SUFFIX_PATTERN.test(basename)) return null;
	if (!hasPosition && !FILE_EXTENSION_PATTERN.test(basename)) return null;
	}
	return candidate;
	}

One workaround: any whitespace inside the backticks disqualifies the span. If you tell the agent (in your AGENTS.md or custom instructions) to write routes together with the method, like GET /api/v1/health, those should render as normal inline code. If you want a real toggle, it's probably worth opening a feature request.