This fixes a regression that caused the VS code extension to be unableto authenticate after making keyring usage on by default. This isbecause the VS code extension assumes the CLI will always use thesession token stored on disk, specifically in the directory specified by--global-config.This fix makes keyring usage enabled when the --global-config directoryis not set. This is a bit wonky but necessary to allow the extension tocontinue working without modification and without backwards compatconcerns. In the future we should modify these extensions to eitheraccess the credential in the keyring (like Coder Desktop) or some otherapproach that doesn't rely on the session token being stored on disk.Tests:`coder login dev.coder.com` -> token stored in keyring`coder login --global-config=/tmp/ dev.coder.com` -> token stored in`/tmp/session`

Closes#20913I've ran the test without the fix, verified the test caught the issue,then applied the fix, and confirmed the issue no longer happens.---🤖 PR was initially written by Claude Opus 4.5 Thinking using Claude Codeand then review by a human 👩

This change filters out non-active tasks from the "Waiting for input"tab filter for the tasks list.---🤖 This change was initially written by Claude Code using Coder Tasks, then reviewed and edited by a human 🏂

Related:#20864

Complete the transition to GA by removing remaining early accessreference in the troubleshooting section.