[Bug] Free tier returns "can only be used from within OpenCode" inside OpenCode Desktop 2.0.32 — persists after restart and full reinstall of both CLI and Desktop; no login option in Desktop #56701

Description

While using the built-in free-tier models inside OpenCode Desktop, the following error suddenly started appearing and now appears consistently:

OpenCode’s free tier can only be used from within OpenCode. Download it at https://opencode.ai and keep building.

I have only ever used the official OpenCode client. I am not using a third-party client, script, proxy, or custom API calls.

The following troubleshooting steps have already been performed, and the error still occurs:

• Restarted OpenCode Desktop: same error

• Fully quit and relaunched: same error

• Uninstalled and reinstalled OpenCode CLI: same error

• Uninstalled and reinstalled OpenCode Desktop: same error

• Restarted Windows: same error

In other words, this is not a temporary or one-off state. The problem reproduces consistently after restarting and after reinstalling both the CLI and Desktop.

Additionally, there is no visible login / authentication entry point in OpenCode Desktop, so I cannot check the current account status, verify whether the free tier is still valid, or re-authenticate from within Desktop.

Steps to reproduce

1. On Windows, use OpenCode Desktop with a built-in free-tier model.

2. Initially it works normally. Then, without changing the client or modifying any configuration, requests start returning the “free tier can only be used from within OpenCode” error.

3. Restart OpenCode Desktop → same error.

4. Uninstall and reinstall OpenCode CLI → same error.

5. Uninstall and reinstall OpenCode Desktop → same error.

6. Restart the system → same error.

7. Look for a login / account / authentication entry point in the Desktop UI → none found.

Expected behavior

• When using the free tier inside official OpenCode Desktop, requests should pass the client validation and should not be rejected as “not an OpenCode client”.

• After a restart or reinstall, the client should return to a working state instead of consistently reproducing the same error.

• Desktop should provide a login / authentication status entry point, or at least give actionable guidance when the free tier fails (e.g., “run opencode auth login in a terminal”), instead of showing only a message that cannot be acted on from within Desktop.

Actual behavior

• Free-tier requests are rejected with the same message used for “non-official client” rejections.

• The issue reproduces consistently after restarting, reinstalling the CLI, reinstalling Desktop, and restarting the system, which indicates it is not caused by cache, a stale session, or a corrupted single installation.

• There is no login entry point in OpenCode Desktop. CLI authentication is done via opencode auth login, with credentials stored in ~/.local/share/opencode/auth.json. It is unclear whether Desktop reuses those credentials, requires separate authentication, or how authentication status can be inspected. Neither the UI nor the documentation makes this clear.

• Users cannot self-diagnose from within Desktop whether the cause is missing authentication, expired credentials, free-tier quota, or missing client request fields causing a false rejection.

Environment

• OpenCode Desktop version: 2.0.32

• OpenCode CLI version: 2.0.32 (replace with the actual output of opencode --version if different)

• Installation method: Desktop installer + CLI (both have been reinstalled)

• OS: Windows (C:\Users\supervisor>)

• Model used: (fill in the exact model ID that triggered the error)

• Custom baseURL / proxy configured: yes / no

• Custom opencode.json configured: yes / no; if yes, please attach a redacted provider configuration

Troubleshooting already attempted

Additional context

• The problem did not exist from the start. It appeared suddenly during normal use, and restarting or reinstalling does not restore normal operation.

• This error is known to mean that a request did not satisfy OpenCode’s client validation requirements. However, in this case the requests are coming from the official Desktop client. It is therefore more likely that the client is omitting required fields in some state, or that Desktop and CLI authentication / session state are inconsistent, rather than the user using a non-official client.

• The lack of any login / authentication status display in Desktop leaves users with no self-service troubleshooting path when this error occurs. At a minimum, Desktop should display authentication status, or when the free tier fails, explicitly suggest running opencode auth login in a terminal and retrying.

When submitting, please attach:

1. Log excerpts from C:\Users\supervisor\.local\share\opencode\log\ around the time of the error;

2. Version confirmation: Desktop 2.0.32 and the output of opencode --version.

The core message is: this is not a case of “didn’t restart” or “didn’t reinstall” — the issue reproduces consistently after restarting and after reinstalling both CLI and Desktop, and Desktop provides no login entry point for troubleshooting.

While using the built-in free-tier models inside OpenCode Desktop, the following error suddenly started appearing and now appears consistently:

OpenCode’s free tier can only be used from within OpenCode. Download it at https://opencode.ai/ and keep building.

I have only ever used the official OpenCode client. I am not using a third-party client, script, proxy, or custom API calls.

The following troubleshooting steps have already been performed, and the error still occurs:

Restarted OpenCode Desktop: same error

Fully quit and relaunched: same error

Uninstalled and reinstalled OpenCode CLI: same error

Uninstalled and reinstalled OpenCode Desktop: same error

Restarted Windows: same error

In other words, this is not a temporary or one-off state. The problem reproduces consistently after restarting and after reinstalling both the CLI and Desktop.

Additionally, there is no visible login / authentication entry point in OpenCode Desktop, so I cannot check the current account status, verify whether the free tier is still valid, or re-authenticate from within Desktop.

Steps to reproduce

On Windows, use OpenCode Desktop with a built-in free-tier model.

Initially it works normally. Then, without changing the client or modifying any configuration, requests start returning the “free tier can only be used from within OpenCode” error.

Restart OpenCode Desktop → same error.

Uninstall and reinstall OpenCode CLI → same error.

Uninstall and reinstall OpenCode Desktop → same error.

Restart the system → same error.

Look for a login / account / authentication entry point in the Desktop UI → none found.

Expected behavior

When using the free tier inside official OpenCode Desktop, requests should pass the client validation and should not be rejected as “not an OpenCode client”.

After a restart or reinstall, the client should return to a working state instead of consistently reproducing the same error.

Desktop should provide a login / authentication status entry point, or at least give actionable guidance when the free tier fails (e.g., “run opencode auth login in a terminal”), instead of showing only a message that cannot be acted on from within Desktop.

Actual behavior

Free-tier requests are rejected with the same message used for “non-official client” rejections.

The issue reproduces consistently after restarting, reinstalling the CLI, reinstalling Desktop, and restarting the system, which indicates it is not caused by cache, a stale session, or a corrupted single installation.

There is no login entry point in OpenCode Desktop. CLI authentication is done via opencode auth login, with credentials stored in ~/.local/share/opencode/auth.json. It is unclear whether Desktop reuses those credentials, requires separate authentication, or how authentication status can be inspected. Neither the UI nor the documentation makes this clear.

Users cannot self-diagnose from within Desktop whether the cause is missing authentication, expired credentials, free-tier quota, or missing client request fields causing a false rejection.

Environment

OpenCode Desktop version: 2.0.32

OpenCode CLI version: 2.0.32 (replace with the actual output of opencode --version if different)

Installation method: Desktop installer + CLI (both have been reinstalled)

OS: Windows (C:\Users\supervisor>)

Model used: (fill in the exact model ID that triggered the error)

Custom baseURL / proxy configured: yes / no

Custom opencode.json configured: yes / no; if yes, please attach a redacted provider configuration

Troubleshooting already attempted

Action Result
Restart OpenCode Desktop Same error
Fully quit and relaunch Same error
Uninstall and reinstall OpenCode CLI Same error
Uninstall and reinstall OpenCode Desktop Same error
Restart Windows Same error
Look for a login entry point in Desktop None found
Additional context

The problem did not exist from the start. It appeared suddenly during normal use, and restarting or reinstalling does not restore normal operation.

This error is known to mean that a request did not satisfy OpenCode’s client validation requirements. However, in this case the requests are coming from the official Desktop client. It is therefore more likely that the client is omitting required fields in some state, or that Desktop and CLI authentication / session state are inconsistent, rather than the user using a non-official client.

The lack of any login / authentication status display in Desktop leaves users with no self-service troubleshooting path when this error occurs. At a minimum, Desktop should display authentication status, or when the free tier fails, explicitly suggest running opencode auth login in a terminal and retrying.

When submitting, please attach:

Log excerpts from C:\Users\supervisor.local\share\opencode\log\ around the time of the error;

Version confirmation: Desktop 2.0.32 and the output of opencode --version.

The core message is: this is not a case of “didn’t restart” or “didn’t reinstall” — the issue reproduces consistently after restarting and after reinstalling both CLI and Desktop, and Desktop provides no login entry point for troubleshooting.