Skip to content

tauri frontend#136

Open
biscoe916 wants to merge 7 commits intostrantalis:mainfrom
biscoe916:biscoe916/spec-section6
Open

tauri frontend#136
biscoe916 wants to merge 7 commits intostrantalis:mainfrom
biscoe916:biscoe916/spec-section6

Conversation

@biscoe916
Copy link

Summary

Adds a Tauri-based desktop frontend (OPUS-tauri-app/) alongside a product specification (docs/tauri-product-spec.md) for the Workset desktop app. Also hardens git command environment isolation and expands env-bootstrap overrides in the Go backend.

Context

  • The Tauri app is a new React + Rust frontend intended to replace the existing Wails + Svelte UI. It implements the core app shell (4-column layout, icon rail, top chrome), Command Center, Spaces (terminal/agent tabs with diff right-panel), and Settings pages, backed by a Rust layer with PTY management, diff engine, session daemon communication, and GitHub integration.
  • The product spec (docs/tauri-product-spec.md) is a working document that defines the mental model (Workset/Workspace/Branch), information architecture, and page-level behavior.
  • Go changes harden non-interactive git execution (GIT_TERMINAL_PROMPT=0) and expand the env-bootstrap override list (HOME, USER, LOGNAME, GIT_ASKPASS, XDG vars) with an increased login-env timeout (2s -> 5s) to improve reliability in automated workflows.

Validation

  • go test ./internal/git/... ./pkg/worksetapi/... — new tests pass for git env hardening and env-snapshot overrides.
  • Tauri app builds and runs locally (`cd OPUS-tauri-app && npm i; npm run tauri dev).
  • Existing make test suite unaffected.

Risks and Rollout

  • New directory (OPUS-tauri-app/): Large addition (~15k LOC); no impact on existing Wails UI or Go CLI — purely additive.
  • Env-bootstrap changes: Expanding the override list and increasing the timeout could affect edge-case shell environments. Mitigated by new test coverage.
  • Spec is a working draft: tauri-product-spec.md will evolve; merging it now establishes a shared reference point.

Review Checklist

  • Tests were added/updated for behavior changes.
  • User-facing docs were updated if behavior changed.
  • Breaking behavior (if any) is documented clearly.
  • If touching large/complex areas, I included rationale and a decomposition follow-up when appropriate.

@biscoe916 biscoe916 requested a review from strantalis as a code owner February 9, 2026 13:42
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 9, 2026

Too many files changed for review. (156 files found, 100 file limit)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant