[Bug]: First install of Desktop, cannot send prompt with `Sign-in required` message

[alejandroiglesias]

GUI version

0.1.29

Operating system

macOS (Apple silicon)

Reproduction steps

On a fresh install, I opened a directory, sent a prompt, and got this Sign-in required message.

The strange part is that I already seem logged in and can see my usage.

Expected behavior

Expected would be to get a response from the model.

Actual behavior

I get this Sign-in required message:

Screenshots, recordings, or sanitized logs

No response

Safety check

• I removed credentials and private project information from this report.

[aliarain]

Thanks for the report and the screenshots, @alejandroiglesias. Sorry about the dead end on a first run.

Two things up front:

1. Your account is fine. The usage panel and the chat use the same sign-in, so this is not a Command Code login problem.
2. That card is misleading. "Sign-in required / Your session expired" is a generic bucket the app shows for any 401 or 403 the model request returns, and it hides the real message. That is on us and we are fixing it: the actual error will be shown, and non-auth refusals (plan or model gating) will stop being labelled as a sign-in problem.

To find what actually failed for you, could you share:

• The provider value in ~/.commandcode/config.json, if there is one. If you also use the CLI and have connected a Claude, Copilot or Codex subscription there, the desktop currently follows that setting and sends your request through that lane, and an expired token on it produces exactly this card. If that is the case, running cmd login anthropic (or your provider) in the CLI and restarting the desktop app should unblock you right away, and we will stop the desktop from inheriting that setting.
• The line starting with Error: from the chat transcript. It is stored under ~/.commandcode/projects/<your-project-folder>/ in the session file for that chat. Please strip anything private before pasting.
• Which model was selected in the composer when you sent the prompt.
• Optionally the tail of ~/Library/Application Support/Command Code/logs/main.log from around the time of the send.

With that we can tell you the exact cause within a reply or two.