Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

If I use --header command to get a needed header to get access to the coder instance then I am unable to start a stopped workspace.

it seems the header was not set so it can not get access and dumps the nonsens warning message invalid charater.

Relevant Log Output

Expected Behavior

Coder CLI should also be aware of header command when starting a stooped workspace. So starting simply works

Steps to Reproduce

1. Wait until a workspace is stopped in local VSCode
2. Reload Window while network was down (has nothing to do with the issue)
3. When VSCode asks to start the stopped workspace say yes
4. Boom

Environment

• Host OS: Manjaro Linux
• Coder version: v2.20.2

Additional Context

No response