What is semantic linking in iTerm2 and how does it work?

Semantic linking in iTerm2 (version 2.9.2+) automatically detects file paths printed to the terminal and makes them clickable. Any file path in terminal output can be Command+clicked to open the file directly in your default editor. This eliminates the need to manually copy paths, switch to your editor, and use "Open File" dialogs, dramatically speeding up navigation between terminal and code.

How do I enable semantic linking in iTerm2?

Semantic linking is built into iTerm2 version 2.9.2 and later—no configuration needed. Simply Command+click any file path that appears in your terminal output and it will open in your default editor. This works with error messages showing file paths, ls output, grep results, or any text that includes valid file paths, making it a powerful productivity boost for developers.

What are common use cases for iTerm2 semantic linking?

Semantic linking excels when navigating compiler errors (click the path in error messages to jump to problematic files), reviewing search results (grep or ripgrep output becomes directly clickable), examining test failures (click paths in test runner output), or exploring directory listings (ls or tree output paths are instantly accessible). This feature eliminates context switching and makes terminal output actionable with a single click.

Published: March 31, 2016

Updated: October 3, 2025

iTerm Semantic Linking

Reading time: 1min

I just learned that iTerm 2 supports semantic linking (at the time of this article I'm on 2.9.2). Now **any file path printed to the terminal can be

⌘+click to open the file in your default editor.**

A gif showing a user clicking on a link in iTerm

Learn more: iTerm2 Documentation
(search in page for semantic)

Build, Scale, Succeed

Join others receiving expert advice on
engineering and product development.

No data sharing. Unsubscribe at any time.

Build, Scale, Succeed

Newsletter Subscription

Related Articles