Browse with agents. Publish with proof. Keep control.
Racore is a local-first agentic browser and open-web protocol desktop app—built with React, Tauri v2, Rust, and Go.
Explore · See the app · Architecture · Quick start · Security
Note
Racore keeps its control plane on your machine. Agents can research and navigate, but meaningful external side effects stop at a human approval boundary.
Most AI browsers optimize for automation. Racore optimizes for agency: the ability to delegate work without giving up identity, credentials, publishing rights, or the final say.
| Capability | What it means | |
|---|---|---|
| ✦ | Agentic workspace | Research, browse, compare, and execute multi-step workflows from one native desktop surface. |
| ◉ | Local control plane | Provider keys, approvals, identity, authority, and peer state stay behind a loopback-only Go service. |
| ✓ | Human checkpoints | Actions that affect the outside world require explicit approval before execution. |
| ⬡ | Verifiable publishing | Sign releases, address content by hash, and carry proof with the work instead of trusting one platform. |
| ◎ | Open network | Discover peers through the Racore mesh and store content through IPFS/Kubo. |
| ⇄ | Provider freedom | Connect cloud models, local models, and coding agents through one consistent gateway. |
|
|
| Discover the system An editorial introduction to the agentic browser and open protocol. |
Choose your boundaries Confirm local AI privacy and network participation before entering. |
The native browser workspace
The same React product workspace runs in hosted preview and native desktop modes. A typed adapter selects the correct transport without changing the daemon request schema:
- Hosted preview → fixed loopback HTTP to
racored. - Tauri desktop → typed
invoke()commands and native events through the Rust backend.
flowchart TB
Human([Human]) -->|goal + approval| React[React 19 workspace]
React -->|typed invoke / events| Tauri[Tauri v2 + Rust]
Tauri -->|allowlisted loopback HTTP| Daemon[racored · Go control plane]
Daemon --> LocalAI[Bundled Hammer 2.0 planner]
Daemon --> Vault[Encrypted local vault]
Daemon --> Authority[Identity + domain authority]
Daemon --> Kubo[IPFS / Kubo]
Daemon --> Mesh[Racore peer mesh]
Mesh <--> Peers[(Verified peers)]
classDef ui fill:#caff2f,stroke:#172018,color:#172018;
classDef native fill:#18231c,stroke:#8fbd22,color:#f4f7ef;
classDef service fill:#0b1110,stroke:#477248,color:#f4f7ef;
class React ui;
class Tauri native;
class Daemon,Providers,Vault,Authority,Kubo,Mesh service;
┌─────────────────────────────────────────────────────────────┐
│ React UI │
│ browser · sites · local AI · network · system │
└──────────────────────────┬──────────────────────────────────┘
│ strongly typed commands + events
┌──────────────────────────▼──────────────────────────────────┐
│ Rust / Tauri v2 │
│ window lifecycle · capability policy · daemon supervision │
└──────────────────────────┬──────────────────────────────────┘
│ fixed origin · allowlisted routes
┌──────────────────────────▼──────────────────────────────────┐
│ racored / Go │
│ approvals · local model planner · authority · protocol │
└──────────┬─────────────────────┬───────────────────────┬────┘
▼ ▼ ▼
AI models IPFS/Kubo peer mesh
Read the deeper architecture guide and Tauri migration audit.
Measured on the same Windows x64 development machine after the Electron → Tauri migration:
| Metric | Electron | Tauri v2 | Improvement |
|---|---|---|---|
| NSIS installer | 211.9 MB | 49.3 MB | 76.7% smaller |
| Application executable | 205.9 MB | 22.4 MB | 89.1% smaller |
| Settled process working set | 337.1 MiB | 131.4 MiB | 61.0% lower |
These are local smoke-test measurements, not universal benchmarks. See the complete verification report for methodology and artifact details.
- Node.js 22.13+
- Rust 1.77.2+ and the Tauri platform prerequisites
- Go 1.22+
- A platform-matching Kubo executable
On Windows, put Kubo at desktop/runtime/kubo/ipfs.exe or set RACORE_KUBO_BINARY. If Go is not on PATH, set RACORE_GO to the executable path.
git clone https://github.com/racore-xyz/racore-browser.git
cd racore-browser
npm install
# Native Tauri application; prepares Go sidecars automatically
npm run desktop:devFor the hosted React preview:
npm run devThe desktop application starts or reuses racored on 127.0.0.1:47831. If Racore discovers a daemon it does not own, it will never terminate it.
# React builds + TypeScript/Node contract tests
npm test
npm run lint
npx tsc --noEmit
# Rust safety and command layer
cargo fmt --manifest-path src-tauri/Cargo.toml -- --check
cargo test --manifest-path src-tauri/Cargo.toml
cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets -- -D warnings
# Existing Go daemon and protocol packages
cd god
go test -count=1 ./internal/...
cd ..
# Native installers + runtime artifact inspection
npm run desktop:package
npm run tauri:verifyRelease bundles are written to src-tauri/target/release/bundle/. Verification rejects any shipped Electron runtime, Node.js runtime, node_modules, .node binding, or node-gyp artifact.
Racore uses Tauri v2 capabilities as a deny-by-default boundary:
- The React webview receives no direct filesystem, OS, shell, or opener plugin permissions.
- Frontend requests cross a typed Rust command surface with Serde payloads.
- Daemon proxying is restricted to fixed loopback origins and explicit route/method pairs.
- External URLs are validated before opening in isolated webview windows.
- Responses are size-limited, and long-running daemon work stays off the UI thread.
- Provider credentials are stored in the local encrypted vault.
- CAPTCHAs, access controls, rate limits, and bans are never bypassed.
See Tauri desktop development for the capability model and release workflow.
racore-browser/
├── app/ # Shared React product UI
├── desktop-ui/ # Static Vite entry for Tauri
├── src-tauri/ # Rust commands, state, windows, capabilities
├── god/ # Go daemon, CLI, protocol, and mesh
├── protocol/ # RCP JavaScript tooling
├── scripts/ # Sidecar prep and bundle verification
├── tests/ # Bridge, scaffold, policy, and bundle tests
├── worker/ # Cloudflare Worker entry
└── docs/ # Architecture, migration, and QA records
- Local first — private state and control live close to the user.
- Human in the loop — delegation never erases consent.
- Private intelligence — the browser planner runs locally without model API keys.
- Proof over promises — identity and releases should be independently verifiable.
- Open infrastructure — content and authority should survive a platform.
Issues, design discussions, and focused pull requests are welcome. Start with CONTRIBUTING.md, keep changes within their architectural layer, and include tests and documentation for behavior changes.
