docs(rfc): propose Tauri desktop control center - #1455
Open
knqiufan wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue or RFC does this PR close?
Refs #1428. This PR proposes the desktop design; implementation and delivery remain tracked by #1428.
Rationale for this change
Users currently need several installation, configuration, and diagnostic surfaces to manage PowerContext. The desktop should provide one native control center while preserving the existing Python Server, public API, and independent service lifecycle.
The proposal chooses Tauri 2 with shared Web presentation and a narrow Rust host. It compares Electron fairly and makes authorization, durable Handoff delivery, installation, and distribution dependencies explicit.
What changes are included in this PR?
Are there any user-facing changes?
Documentation-only design proposal. This PR does not change runtime behavior, public APIs, dependencies, or persisted formats. The RFC distinguishes a personal preview from the full collaboration and delivery requirements for #1428.
How was this change tested?
uv lock --check.uv run --locked prek run --all-files, including the configuredty checkhook.python -m zensical build --clean -susing the project virtual environment and an isolated tracked-source snapshot with the proposed documentation. Verified the generated API landing page and byte-for-byte equality of the published OpenAPI contract, matching themake docs-testartifact checks.git diff --check.AI usage statement
OpenAI Codex assisted with repository and issue research, drafting and translating the RFC, validation, and PR preparation.