We've seen feedback that the current behavior of this command is confusing.

• Piping output of coder templates pull to a file renders as a binary/unsupported text encoding #3398
• coder template pull <name> does not pull as a folder #2651

I don't have an exact solution in mind, but I know that piping the tar into sdout is not a solution we should stick with.

Some ideas:

• Rewrite template stuff to mimic git clone / git pull behavior
• Download to a folder by default
• Require the user to specify a tar file (or help the user with coder templates pull | tar -xf)