This PR fixes an issue #9563 where relative file paths were not being resolved against the terminal’s current working directory before opening. #### Verification Tested with directories containing: ``` /tmp/test/test ❯ du -h . 0B ./spaces-end 0B ./with dot. 0B ./space middle 8.0K . ``` Parent directory resolution also works as expected: ``` /tmp/test/test ❯ du -h .. 0B ../test/spaces-end 0B ../test/with dot. 0B ../test/space middle 8.0K ../test 16K .. ``` @mitchellh In your original description you mentioned that “Links should work for all situations as they do in iTerm2.” I noticed that, for example, when running `ls`, the paths are not clickable, while they are clickable in iTerm2. If you think this case should also be handled, I can open a separate PR for it once this one is accepted.