What task are you trying to do?
Keep PawWork GUI-only by removing unused TUI and Tauri compatibility code that no longer belongs to the product surface.
What do you do today?
The repository still carries terminal UI and Tauri-era code even though PawWork now ships as an Electron GUI application. This increases the amount of code that needs to be checked during upstream sync and makes future cherry-picks harder to review because unrelated TUI/Tauri changes can appear in the diff.
What would a good result look like?
PawWork keeps only the GUI and embedded server paths it actually uses. Tauri compatibility leftovers are removed where they are no longer needed. TUI code is removed through a deliberate cleanup that first disconnects build entries, server routes, generated SDK surfaces, plugin exports, config files, and tests so the Electron GUI path remains working.
Which audience does this matter to most?
Both
Extra context
Initial read-only check found Tauri leftovers in the Electron migration/titlebar/CORS compatibility areas and TUI references in the opencode build script, server /tui routes, config, plugin types, tests, and OpenTUI dependencies. Suggested split: first remove low-risk Tauri compatibility leftovers, then remove TUI in a second scoped change after confirming the GUI does not call /tui APIs and replacing any TUI-only event usage such as MCP toast publishing.
What task are you trying to do?
Keep PawWork GUI-only by removing unused TUI and Tauri compatibility code that no longer belongs to the product surface.
What do you do today?
The repository still carries terminal UI and Tauri-era code even though PawWork now ships as an Electron GUI application. This increases the amount of code that needs to be checked during upstream sync and makes future cherry-picks harder to review because unrelated TUI/Tauri changes can appear in the diff.
What would a good result look like?
PawWork keeps only the GUI and embedded server paths it actually uses. Tauri compatibility leftovers are removed where they are no longer needed. TUI code is removed through a deliberate cleanup that first disconnects build entries, server routes, generated SDK surfaces, plugin exports, config files, and tests so the Electron GUI path remains working.
Which audience does this matter to most?
Both
Extra context
Initial read-only check found Tauri leftovers in the Electron migration/titlebar/CORS compatibility areas and TUI references in the opencode build script, server /tui routes, config, plugin types, tests, and OpenTUI dependencies. Suggested split: first remove low-risk Tauri compatibility leftovers, then remove TUI in a second scoped change after confirming the GUI does not call /tui APIs and replacing any TUI-only event usage such as MCP toast publishing.