From 211db63f51a494f8e6bcb2865092775f57849d5a Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Mon, 16 Nov 2026 16:56:21 +0200 Subject: claude memory: keep file paths out of terminal link detection --- config/claude/CLAUDE.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) (limited to 'config') diff --git a/config/claude/CLAUDE.md b/config/claude/CLAUDE.md index b4eb2f6..f6e571e 100644 --- a/config/claude/CLAUDE.md +++ b/config/claude/CLAUDE.md @@ -40,3 +40,22 @@ and the cleanup had not. `kill-window`: an error there is the warning that it went somewhere else. - **A test harness that starts tmux gives it its own `-L` socket.** Without one its sessions land in the operator's server and its cleanup runs there. + +# File paths in prose: keep the terminal's link detection out of it + +Agents here usually run in Ghostty (often under tmux), whose click-to-open +matcher reads the raw screen text. A sentence that ends directly after a file +path makes the matcher include the sentence's final period in the path — +clicking `/Users/sz/x/lsd-v3-deployments/web-research/deviations.md.` then +fails, and Ghostty reports the target does not exist. + +So when mentioning a file path in prose: + +- Never end a sentence directly after a bare path. Follow it with a colon, a + parenthesis, or nothing — not a period. +- Prefer wrapping the path in backticks; the match stops at the closing + backtick. +- Best: make it a markdown link to the absolute `file://` URL, for example + `[deviations.md](file:///Users/sz/x/lsd-v3-deployments/web-research/deviations.md)`, + which renders as an OSC 8 hyperlink whose destination is exact and immune to + surrounding punctuation. -- cgit v1.2.3