[TUI] The preconfigured OpenCode configuration block is broken as it uses legacy field names
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cpp
- Domain
- cli, developer-experience
Research direction
Find the TUI tab 7 (Connect) code that generates the preconfigured OpenCode block. Update the provider and model fields to match the V2 names and structure shown in the issue. Check the generated block against that example and verify that it no longer uses the listed V1 fields.
Written by the indexing model from the issue text.
Description
Problem
After pasting in opencode.jsonc the OpenCode configuration block offered by tab#7 (Connect) in the TUI, the model is not working in OpenCode
Environment
any environment using the latest version of OpenCode
Reproduced on Windows 11, RTX 2070 8GB, 32GB RAM
Reproduce
- Copy/paste the preconfigured configuration block for OpenCode offered by Strata TUI in the appropriate opencode.jsonc configuration file
- launch OpenCode and select the target Strata model to use
- begin operation
Expected: Strata responds and interacts with OpenCode
Actual: OpenCode throws an error message and does not communicate with Strata
Root cause
The strata provider in the precompiled block is using OpenCode V1 field names (npm, options) and V1 model capability fields (tool_call, reasoning) instead of the OpenCode V2 equivalents (package, settings, capabilities).
Evidence
The following OpenCode autoconfig block is produced by Strata TUI:
"strata": {
"npm": "@ai-sdk/openai-compatible",
"name": "Strata (local)",
"options": {
"baseURL": "http://127.0.0.1:8080/v1",
"apiKey": "sk-strata-key"
},
"models": {
"qwen3.8-flash-next-gyro-gyro-s": {
"name": "Qwen3.8-Flash-Next (local)",
"tool_call": true,
"reasoning": true,
"limit": {
"context": 131072,
"input": 126976,
"output": 4096
}
}
}
}
That uses the legacy OpenCode v1 syntax that is not accepted by the current OpenCode version.
The same configuration block shall be corrected as follows:
"strata": {
"name": "Strata (local)",
"package": "@ai-sdk/openai-compatible",
"settings": {
"baseURL": "http://127.0.0.1:8080/v1",
"apiKey": "sk-strata-key"
},
"models": {
"qwen3.8-flash-next-gyro-gyro-s": {
"name": "Qwen3.8-Flash-Next (local)",
"capabilities": {
"tools": true,
"reasoning": {
"supported": true
},
"input": ["text"],
"output": ["text"]
},
"limit": {
"context": 131072,
"input": 126976,
"output": 4096
}
}
}
}
- Dominant language
- C++
- Stars
- 11.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Niko1221/Strata
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
Similar issues
-
Shell: serve the home app's Cookie Policy on a hard reloadPossibly taken @2001anshkaushik claimed this today. Openfeature module:ai
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
rocketride-org/rocketride-server#2899 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rice-solar-physics/HYDRAD#113 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PX4/PX4-Autopilot#29496 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
madskristensen/FileIcons#385 ·