Remote ACP Bridge: a Tauri 2 app that lets websites use your local coding agent (with WebDriver tests on Windows/Linux) #16452
brstic
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Remote ACP Bridge is an open-source (Apache-2.0) Tauri 2 desktop app that lets websites you approve send tasks to the AI coding agent on your own computer (Codex or Claude Code, through the Agent Client Protocol). You stay in control: you approve each site, choose one project folder, approve each task, and answer every permission prompt locally.
Repo: https://github.com/brstic/remote-acp · Release (macOS / Windows / Linux): https://github.com/brstic/remote-acp/releases/tag/v0.1.0
Tauri bits that might be useful to others:
bridge-core). It spawns agent subprocesses, speaks JSON-RPC over stdio, and holds policy. The Tauri layer is thin commands plus events. That made it easy to test headlessly, including a fake "desktop" for end-to-end tests.remoteacp://pair?…) viatauri-plugin-deep-linkandtauri-plugin-single-instance. One gotcha: with two installed copies of the app (debug and release), macOS may route the link to the copy that isn't running, and the single-instance hand-off drops the URL.RunEvent::Reopenbrings it back from the Dock, and quitting from the tray shuts the agents down cleanly.tauri-driver+ WebKitWebDriver under Xvfb) and on Windows. On Windows,tauri-driver's launch failed with "DevToolsActivePort file doesn't exist", because Tauri sets its own WebView2 browser args, soWEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTSis ignored. What worked: create the main window in code, addadditional_browser_args("--remote-debugging-port=…")only in debug builds behind an env var, start the app yourself, and attachmsedgedriverwithms:edgeOptions.debuggerAddress. Seetests/desktop-webdriver/run.mjsand.github/workflows/ci.yml.Feedback welcome!
All reactions