Showing the changes to docs/user (1 of 42 files). Show all
Unified · Split
| @@ -0,0 +1,53 @@ | ||
| 1 | +# OpenCode | |
| 2 | + | |
| 3 | +T3 Code uses the OpenCode setup on the connected environment. With a remote environment, its | |
| 4 | +OpenCode login and configuration apply, not the setup on your desktop or phone. | |
| 5 | + | |
| 6 | +T3 Code requires OpenCode 1.14.19 or newer. It checks the server version before it loads models or | |
| 7 | +starts work. If the check fails, update OpenCode or fix the server URL and password, then refresh | |
| 8 | +the provider status. Reconnecting the client also runs the check again. | |
| 9 | + | |
| 10 | +## Server authentication | |
| 11 | + | |
| 12 | +Without a server URL, T3 Code starts a local OpenCode server. The process inherits | |
| 13 | +`OPENCODE_SERVER_PASSWORD` from the environment. A password in the provider settings overrides | |
| 14 | +that environment value for both the local process and T3 Code. | |
| 15 | + | |
| 16 | +With a server URL, T3 Code connects to that external server and uses only the password in the | |
| 17 | +provider settings. It does not send a local `OPENCODE_SERVER_PASSWORD` to an external server. | |
| 18 | +OpenCode uses this password for HTTP Basic authentication. | |
| 19 | + | |
| 20 | +## Refresh the model list | |
| 21 | + | |
| 22 | +T3 Code loads the model list when an enabled OpenCode provider starts and keeps the list in its | |
| 23 | +cache. Reconnecting a client or using a refresh control asks OpenCode for the list again. The | |
| 24 | +periodic provider health setting does not refresh OpenCode's catalog. | |
| 25 | + | |
| 26 | +After changing an OpenCode login or configuration outside T3 Code, open **Settings > Providers**, | |
| 27 | +select the environment, and choose **Refresh provider status**. Changing the provider's | |
| 28 | +configuration in T3 Code also replaces that provider connection. | |
| 29 | + | |
| 30 | +On mobile, open the thread settings and select **Refresh models**. The control stays disabled while | |
| 31 | +the refresh runs and shows an error if the refresh fails. | |
| 32 | + | |
| 33 | +OpenCode reads credential changes on each model-list request. Native OpenCode configuration files | |
| 34 | +can stay cached while the local helper is running. The helper closes after 30 seconds with no | |
| 35 | +model-list or text-generation work. Refresh after that idle period to start a new helper and read | |
| 36 | +the file changes. Repeated refreshes or active helper work can extend this wait. | |
| 37 | + | |
| 38 | +T3 Code does not own an external OpenCode server. Native configuration changes on that server can | |
| 39 | +require its own reload or restart before a refresh returns the new list. | |
| 40 | + | |
| 41 | +If a refresh fails, T3 Code keeps the last known models, slash commands, and skills. Fix the | |
| 42 | +connection, then refresh again. A successful refresh can remove entries that OpenCode no longer | |
| 43 | +offers. | |
| 44 | + | |
| 45 | +## Continue an existing thread | |
| 46 | + | |
| 47 | +An existing thread keeps its selected model and options when that model is temporarily absent | |
| 48 | +from the catalog. The web picker shows an **Unavailable** row and keeps saved option values visible | |
| 49 | +until the model metadata returns. T3 Code does not switch the thread to the first model in the | |
| 50 | +list. | |
| 51 | + | |
| 52 | +The stored selection does not guarantee that OpenCode can still run the model. If the provider | |
| 53 | +rejects it, select an available model before trying again. | |