Description
Editing the value of the first color variable in the list (the one at sort_order: 0) through the Ycode editor UI does not persist. The color picker appears to accept the change visually, but the value reverts on reload. All other color variables (sort_order 1, 2, etc.) and newly created variables save correctly.
Steps to reproduce
1 Open the Ycode editor and navigate to Color Variables
2 Create at least 2–3 color variables (e.g. "Charcoal" #0a0a0a, "White" #ffffff, "Dark Grey" #323232)
3 Click on the first color variable in the list (the one at index 0 / sort_order 0)
4 Change its value to a different color (e.g. from #0a0a0a to #1a1a2e)
5 Save / close the panel
6 Reload the page or re-open the color variables panel
Expected behavior
The first color variable should reflect the updated value (#1a1a2e) after reload, the same way all other variables do.
Actual behavior
The first color variable reverts to its original value (#0a0a0a). The change is silently discarded , no error is shown.
Screenshots or screen recordings
No response
Deployment type
Self-hosted
Browser
Brave 1.88.134
Operating system
macOS 26.3.1
Additional context
The API/database layer works fine. Updating the same variable via the MCP tool (update_color_variable) persists correctly and is reflected in subsequent reads. This confirms the issue is isolated to the front-end UI save handler, not the database.
All other variables work. Editing the 2nd, 3rd, or any newly created color variable via the UI saves as expected. Only the variable at sort_order: 0 is affected.
Workaround: Edit the value directly in Supabase, or use the MCP update_color_variable tool.
Description
Editing the value of the first color variable in the list (the one at sort_order: 0) through the Ycode editor UI does not persist. The color picker appears to accept the change visually, but the value reverts on reload. All other color variables (sort_order 1, 2, etc.) and newly created variables save correctly.
Steps to reproduce
1 Open the Ycode editor and navigate to Color Variables
2 Create at least 2–3 color variables (e.g. "Charcoal" #0a0a0a, "White" #ffffff, "Dark Grey" #323232)
3 Click on the first color variable in the list (the one at index 0 / sort_order 0)
4 Change its value to a different color (e.g. from #0a0a0a to #1a1a2e)
5 Save / close the panel
6 Reload the page or re-open the color variables panel
Expected behavior
The first color variable should reflect the updated value (#1a1a2e) after reload, the same way all other variables do.
Actual behavior
The first color variable reverts to its original value (#0a0a0a). The change is silently discarded , no error is shown.
Screenshots or screen recordings
No response
Deployment type
Self-hosted
Browser
Brave 1.88.134
Operating system
macOS 26.3.1
Additional context
The API/database layer works fine. Updating the same variable via the MCP tool (update_color_variable) persists correctly and is reflected in subsequent reads. This confirms the issue is isolated to the front-end UI save handler, not the database.
All other variables work. Editing the 2nd, 3rd, or any newly created color variable via the UI saves as expected. Only the variable at sort_order: 0 is affected.
Workaround: Edit the value directly in Supabase, or use the MCP update_color_variable tool.