In MacOS, possible to open WezTerm.app in specified dir?

[seph-barker]

I'd like to be able to open WezTerm, provided with a directory, and have WT startup with that directory as CWD. Specifically, when initializing like this (in MacOS): open $DIR -a /Applications/WezTerm.App. Currently if I do this, WT just echoes $DIR ; exit and then immediately closes.

The behavior I want is exactly what happens if you invoke this command with iTerm and the default MacOS terminal.

I'm aware that I can get the behavior I want by invoking like wezterm start --cwd $DIR, but this doesn't work for my needs. I'm trying to invoke this behavior from a different application (a Raycast plugin) that doesn't allow me to configure the opening behavior (it just uses some default Mac opening commands).

Not sure if the existing behavior is implemented as is for some explicit reason, but if not I'd love for it to be changed to the behavior I want. :-)

[techyogi]

Works great - i use this: https://github.com/Ji4n1ng/OpenInTerminal and set up a keyboard shortcut so that if i command-shift-T in a finder window, it opens in that directory

[seph-barker]

Hey thanks for the suggestion. Looks like a cool tool, but I can't figure out a way to get it to work for my usecase. In this case, I have a plugin that lists a bunch of git repos and then lets you open them in an app of your choice. I can't configure how that app is invoked, just select which one to use. The app is invoked equivalent to running open $DIR -a $APP.

Unfortunately running open $DIR -a /Applications/OpenInTerminal.app just produces an errror. :-(

[seph-barker]

For posterity, I was able to solve this for myself by creating a simple Automator app that invokes the following:

WEZTERM_UNIX_SOCKET=~/.local/share/wezterm/default-org.wezfurlong.wezterm wezterm cli spawn --cwd "$DIR"

Obviously that works for my particular flow (opens a new tab in a single existing window), other people might want a different flow. It'd be kind of nice if this were integrated by default into WezTerm.app, and I think my flow is probably the sensible default one on Macs (with the additional behavior that it should spawn a new window if one doesn't already exist). But if you decide it's not worth adding this Automator approach works for me.