dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

moved from tauri to a server with embedded UI

Browse Source
This commit is contained in:
Dave
2026-02-13 12:31:36 +00:00
parent d4203cfaab
commit 0876c53e17
79 changed files with 5755 additions and 10655 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
.living_spec/stories/archive/24_tauri_to_browser_ui.md Normal file
View File

@@ -0,0 +1,23 @@
# Story 01: Replace Tauri with Browser UI Served by Rust Binary
## User Story
As a user, I want to run a single Rust binary that serves the web UI and exposes a WebSocket API, so I can use the app in my browser without installing a desktop shell.
## Acceptance Criteria
- The app runs as a single Rust binary that:
- Serves the built frontend assets from a `frontend` directory.
- Exposes a WebSocket endpoint for chat streaming and tool execution.
- The browser UI uses the WebSocket API for:
- Sending chat messages.
- Receiving streaming token updates and final chat history updates.
- Requesting file operations, search, and shell execution.
- The project selection UI uses a browser file picker (not native OS dialogs).
- Model preference and last project selection are persisted server-side (no Tauri store).
- The Tauri backend and configuration are removed from the build pipeline.
- The frontend remains a Vite/React build and is served as static assets by the Rust binary.
## Out of Scope
- Reworking the LLM provider implementations beyond wiring changes.
- Changing the UI layout/visual design.
- Adding authentication or multi-user support.
- Switching away from Vite for frontend builds.