Dashboard v2 silently rolled out, API keys no longer work, forcing upgrade

Description

Dashboard v2 has been rolled out slowly without opt in. No communication about it. It is destroying workflows and forcing users to upgrade because their API keys do not work anymore.

I upgraded from 1.18.21 to current latest 1.18.31, did opencode console login, and that finally made the rate limit error go away. But there is a caveat. The usage logs on dashboard v2 show User (email) instead of the API keys, both Legacy and the new one I created on dashboard v2.

I also created a new service account on dashboard v2, created a new API key, inserted it in my auth.json under "opencode": { "type": "api", "key": "" }. Those did not work.

Related issues:

• #49755: "New OpenCode Console fails to load workspace budget, inference attempt also says Free usage exceeded despite not using any free models in the past 24 hours"
• #49751: "New OpenCode Console just lost all my inference Logs"

On #49755 I commented:

Update: Upgrade from 1.18.21 to current latest 1.18.31, did opencode console login, that finally made the rate limit error go away. But there is a caveat: the usage logs on dashboard v2 show User (email) instead of the API keys. Both Legacy and the new dashboard v2 key. I also created a new service account on dashboard v2 and a new API key, inserted it in my auth.json under "opencode": { "type": "api", "key": "" } those did not work. See this issue for full details.

On #49751 I commented:

Looks like this is related to dashboard v2 being silently rolled out without opt in. No communication about it, and it is destroying workflows. The usage logs on dashboard v2 show User (email) instead of API keys, and my keys stopped working because of it. See this issue for full details.

Plugins

No response

OpenCode version

1.18.31

Steps to reproduce

1. Upgrade from 1.18.21 to current latest 1.18.31
2. Do opencode console login
3. Notice the rate limit error goes away
4. Try creating a new service account on dashboard v2
5. Create a new API key, insert it in auth.json under "opencode": { "type": "api", "key": "" }
6. See that it still does not work, both Legacy and new dashboard v2 key get 429 RateLimit.FreeUsageLimitError
7. Check dashboard v2 logs, see User (email) recorded instead of API keys

Screenshot and/or share link

Operating System

Windows 10

Terminal

Windows Terminal

Start by reproducing the reported upgrade from 1.18.21 to 1.18.31, then compare opencode console login with the API key and service-account values in auth.json. Trace the authentication entry points and the dashboard v2 usage-log data path. Done means valid legacy and dashboard v2 keys no longer receive 429 RateLimit.FreeUsageLimitError and usage logs identify the expected credential.