If you were to somehow get a 401, or some other unexpected HTTP status code when following a workspace's build logs,coder ssh would swallow the error, and give you a different error that didn't make sense.
In this case I was getting a 401 on/templateversions/{templateversion}/dry-run/{jobID}/logs , but the CLI error would say the workspace had no agents.

I ran into the 401 when running a scaletest, and then whilst attempting to reproduce the issue locally, I rancoder ssh from one build of Coder that usedcoder_session_token as the session token cookie name, whilst the other build useddev_coder_session_token (as set bydevelop.sh). For reference, the CLI uses cookies when following the build logs.