openhuman/gitbooks/developing/tauri-shell/core-bridge.md

description, icon

description	icon
How the Tauri shell talks to the openhuman core sidecar — process lifecycle and HTTP JSON-RPC.	bridge

Core bridge & helpers (app/src-tauri)

This document replaces the old “SessionService / SocketService” split. The Tauri crate does not embed a duplicate Socket.io server or Telegram client; instead it focuses on process management and HTTP JSON-RPC to the openhuman binary.

CoreProcessHandle (core_process.rs)

• Resolves the openhuman executable (staged under binaries/ or PATH / dev layout).
• Starts or attaches to the core process and exposes its RPC URL (OPENHUMAN_CORE_RPC_URL).
• Used during app setup in lib.rs (app.manage(core_handle)).

core_rpc (core_rpc.rs)

• HTTP client for the core’s JSON-RPC surface (localhost).
• Used by core_rpc_relay to forward method + params from the frontend.

commands/core_relay.rs

• core_rpc_relay — ensures the core is running (in-process handle or service-managed path), then calls core_rpc.
• ensure_service_managed_core_running — bootstraps systemd/launchd-style service when RPC is down (platform-specific behavior inside core CLI).

commands/openhuman.rs

• Daemon host JSON config (e.g. tray visibility) under the app data directory.
• Install/start/stop/status/uninstall helpers for the openhuman background service.

utils/dev_paths.rs

• Resolves src/openhuman/agent/prompts for development and bundled resource paths for AI preview.

utils/tauriSocket.ts (frontend)

Not in src-tauri, but pairs with the shell: the React app listens for Tauri events that mirror socket activity when using the Rust-side client. See app/src/utils/tauriSocket.ts and the Frontend Services chapter.

---

Previous: Commands