Is there any documentation or references about this sequence?

Not super formally documented, but I've made a round-up of terminals supporting OSC 7 with links to their documentation or implementations in charmbracelet/sequin#24.

For formal documentation specifically:

• macOS Terminal: Screenshot in OSC 7 notify working directory support sequin#24
• iTerm2: https://iterm2.com/documentation-escape-codes.html
• WezTerm: https://wezfurlong.org/wezterm/shell-integration.html#osc-7-escape-sequence-to-set-the-working-directory

There's also this blog article I've come across documenting the escape sequence.

For formal documentation specifically:

• macOS Terminal: Screenshot in OSC 7 notify working directory support sequin#24
• iTerm2: https://iterm2.com/documentation-escape-codes.html
• WezTerm: https://wezfurlong.org/wezterm/shell-integration.html#osc-7-escape-sequence-to-set-the-working-directory

There's also this blog article I've come across documenting the escape sequence.

No worries, I would just include the iterm2 and wezterm links in the code comments.

No worries, I would just include the iterm2 and wezterm links in the code comments.

Done in 52210b9, how's that look?

Looks good! Could you please update the imports and format the file using gofumpt?

Done!

BTW if you want to see this in action for yourself, I wrote this quick script that should let you Ctrl/Cmd+Click the ../main.go path (tested with VSCode and iTerm2) if you place it at the root of the repo and run it with go run main.go:

package main

import (
	"fmt"
	"os"
	"path/filepath"
	"runtime"

	"github.com/charmbracelet/x/ansi"
)

func main() {
	_, filename, _, ok := runtime.Caller(0)
	if !ok {
		panic("no caller")
	}
	dir := filepath.Dir(filename)
	fmt.Println("changing cwd OSC 7 to " + dir)
	fmt.Printf(ansi.NotifyWorkingDirectory("localhost", dir, "ansi"))
	fmt.Println("../main.go:13:5: error: use of undeclared identifier 'sdfsfds'")
	termProgram := os.Getenv("TERM_PROGRAM")
	if termProgram == "vscode" {
		fmt.Println("Hello, VSCode needs an extra line for some reason (don't need this for iTerm2)")
	}
}

Thank you, @rzhw! This will be included in ansi/v0.5.2