I’m not entirely sure that the glob expansion will work here, since Nova does not invoke things within an interactive terminal (just a login shell) which could perform the expansion. But we can investigate!
I also noticed the same problem using shell string quotes. To solve the edge case of a file with a name that starts with a space character in a real terminal you can do ' file.txt' as an arg, but with TaskProcessAction the arg ends up including the string quotes in the value. I wanted to basically take a Nova workspace config path value and dump it between two quotes so a user can type in filenames that begin with a space, which is a little weird but perfectly valid input.
Sorry I don’t have a precise example handy; it was 4 days ago now and I forget exactly what the full shell script was.
Without the ability to have our shell scripts interpreted properly, I’m not sure how we can deal with certain things like this. I actually gave up on Nova task templates over it, manually configured tasks can do more.