Clarify active Windows client architecture
This commit is contained in:
@@ -1,5 +1,12 @@
|
||||
# Windows Client Implementation Plan
|
||||
|
||||
> Superseded: do not execute this Node `APP_MODE=windows` plan as the current
|
||||
> Windows implementation path. The active plan is the standalone Tauri 2 desktop
|
||||
> app in `docs/goals/windows-modular-client/PLAN.md`, based on
|
||||
> `docs/windows-client-product-tech-brief.md`.
|
||||
> Content below is retained for historical context and may contradict the active
|
||||
> Tauri plan.
|
||||
|
||||
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
|
||||
|
||||
**Goal:** Restore the Windows proxy workflow as a script-first product with two install modes: full local `sing-box` + ProxiFyre, or ProxiFyre-only routing to an existing proxy, controlled by a clean local web UI.
|
||||
|
||||
@@ -1,5 +1,12 @@
|
||||
# Windows Client Design
|
||||
|
||||
> Superseded: this document describes the earlier Node/web-control Windows direction.
|
||||
> The active Windows direction is a standalone Tauri 2 desktop app under
|
||||
> `apps/windows-client`, driven by `docs/windows-client-product-tech-brief.md`
|
||||
> and `docs/goals/windows-modular-client/PLAN.md`.
|
||||
> Content below is retained for historical context and may contradict the active
|
||||
> Tauri plan.
|
||||
|
||||
## Goal
|
||||
|
||||
Restore the old Windows workflow in a cleaner product shape: a one-command PowerShell installer can install either a full local `sing-box` + ProxiFyre setup or ProxiFyre-only routing to an existing proxy, then expose a small local web UI for profiles, folders, executable files, status, and logs.
|
||||
|
||||
Reference in New Issue
Block a user