anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-23 10:45:33 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

opentui: config unrecognized keys #2350

New Issue
Closed
opened 2026-02-16 17:35:16 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 17:35:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @jeeeem on GitHub (Oct 29, 2025).

Description

Error: Config file at /Users/redacted/.config/opencode/opencode.jsonc is invalid
↳ Unrecognized keys: "app_help", "switch_mode", "session_child_cycle", "session_child_cycle_reverse", "tool_details", "thinking_blocks", "project_init" keybinds

Does opentui has different config schema options?

OpenCode version

0.0.0-opentui-202510292344

Steps to reproduce

Use latest opentui

Screenshot and/or share link

No response

Operating System

macOS 26.0.1

Terminal

ghostty

Originally created by @jeeeem on GitHub (Oct 29, 2025). ### Description ``` Error: Config file at /Users/redacted/.config/opencode/opencode.jsonc is invalid ↳ Unrecognized keys: "app_help", "switch_mode", "session_child_cycle", "session_child_cycle_reverse", "tool_details", "thinking_blocks", "project_init" keybinds ``` Does opentui has different config schema options? ### OpenCode version 0.0.0-opentui-202510292344 ### Steps to reproduce Use latest opentui ### Screenshot and/or share link _No response_ ### Operating System macOS 26.0.1 ### Terminal ghostty
yindo added the bug label 2026-02-16 17:35:16 -05:00
yindo closed this issue 2026-02-16 17:35:16 -05:00
yindo commented 2026-02-16 17:35:17 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Oct 29, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #855: [Unrecognized key(s) binds] - Very similar config validation error with unrecognized keybind names like 'help', 'history_previous', 'history_next'. Both issues involve invalid keybind configuration in opencode.jsonc/config.json files.

The root cause appears to be the same - certain keybind names that were valid in older versions are no longer recognized by the current config schema, particularly affecting OpenTUI builds.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Oct 29, 2025): This issue might be a duplicate of existing issues. Please check: - #855: [Unrecognized key(s) binds] - Very similar config validation error with unrecognized keybind names like 'help', 'history_previous', 'history_next'. Both issues involve invalid keybind configuration in opencode.jsonc/config.json files. The root cause appears to be the same - certain keybind names that were valid in older versions are no longer recognized by the current config schema, particularly affecting OpenTUI builds. Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:35:17 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Oct 29, 2025):

Yeah this is expected: https://github.com/sst/opencode/blob/opentui/CHANGES.md#breaking-changes

U can use this file to track what changes^ Things are still in flux atm

@rekram1-node commented on GitHub (Oct 29, 2025): Yeah this is expected: https://github.com/sst/opencode/blob/opentui/CHANGES.md#breaking-changes U can use this file to track what changes^ Things are still in flux atm
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2350
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?