feat(remote): proxy core commands via daemon#121
Merged
Dimillian merged 4 commits intoDimillian:mainfrom Jan 20, 2026
Merged
Conversation
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.
Part of the optional remote backend mode RFC (#54).
What
Adds a Tauri-side remote backend proxy layer that can (optionally) forward a subset of backend commands to the daemon introduced in #58.
src-tauri/src/remote_backend.rsWhy
This is the next incremental step after:
backendMode,remoteBackendHost,remoteBackendToken)The goal is to allow the UI to keep using the same Tauri commands/events, while the Rust side can swap between:
local(current behaviour)remote(daemon over localhost JSON-RPC)Notes
backendMode=remote.Validation
npm cinpm run typechecknpm run buildRust compilation/tests require platform WebKitGTK deps on Linux; CI should cover this.