mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-06-19 10:02:16 +00:00
8eedb50bce
Hermes-Setup.exe is a small signed Rust+Tauri binary that drives
scripts/install.ps1 stage-by-stage with a native UI matching the
desktop's design language. Replaces the chicken-and-egg pattern of
shipping a 200MB Electron app whose first launch existed only to
run install.ps1.
The architecture:
Rust backend (src-tauri/):
bootstrap.rs orchestrator -- Tauri commands, stage iteration
install_script.rs resolve install.ps1 (dev checkout, cache, GitHub raw)
powershell.rs spawn powershell, line-stream stdout/stderr, parse JSON
events.rs BootstrapEvent types -- mirror bootstrap-runner.cjs
paths.rs HERMES_HOME resolution + tracing log setup
build.rs bakes BUILD_PIN_COMMIT / BUILD_PIN_BRANCH from
'git rev-parse HEAD' at compile time
React frontend (src/):
Tauri webview rendering 4 screens (welcome / progress / success /
failure), driven by nanostores subscribing to the Rust event stream.
Visual layer reuses the desktop's styles.css wholesale via @import
so the installer and desktop never drift visually.
Distribution:
targets = ['app', 'dmg', 'appimage'] -- no NSIS/MSI wrapper. The
raw target/release/Hermes-Setup.exe IS the artifact on Windows;
.dmg + .app on macOS; AppImage on Linux. One file, double-click,
no installer-installing-an-installer pattern.
Compile-time pinning:
build.rs reads 'git rev-parse HEAD' and emits
cargo:rustc-env=BUILD_PIN_COMMIT=<sha> + BUILD_PIN_BRANCH=<branch>.
bootstrap.rs's option_env!() picks these up so the binary fetches
install.ps1 from the exact SHA it was tested against. CI / release
builds can override via HERMES_BUILD_PIN_COMMIT env var.
Windows manifest:
hermes-setup.manifest declares level='asInvoker' so the
productName 'Hermes Setup' doesn't trip Windows's installer-
detection heuristic and refuse to launch without elevation.
Also declares PerMonitorV2 DPI + UTF-8 active code page + Common
Controls v6.
Limitations of this initial version:
* No code signing -- Windows SmartScreen will warn once on Hermes-Setup.exe
('More info -> Run anyway'). The downstream binaries it produces
(Hermes.exe in win-unpacked/, the hermes CLI) are locally-built and
therefore don't carry MOTW, so they launch without SmartScreen
intervention. Cert procurement tracked separately.
* macOS and Linux build paths defined but untested -- Windows-only V1.
35 lines
1.1 KiB
TypeScript
35 lines
1.1 KiB
TypeScript
import { useStore } from '@nanostores/react'
|
|
import { useEffect } from 'react'
|
|
import { $route, $bootstrap, initialize } from './store'
|
|
import Welcome from './routes/welcome'
|
|
import Progress from './routes/progress'
|
|
import Success from './routes/success'
|
|
import Failure from './routes/failure'
|
|
|
|
/*
|
|
* App shell — Hermes Setup.
|
|
*
|
|
* No header chrome (the OS title bar already says "Hermes Setup"; an
|
|
* in-window repeat of the H mark + words was redundant slop).
|
|
*
|
|
* Route state lives in a single $route atom — 4 screens, no react-router.
|
|
*/
|
|
export default function App() {
|
|
const route = useStore($route)
|
|
const bootstrap = useStore($bootstrap)
|
|
|
|
useEffect(() => {
|
|
void initialize()
|
|
}, [])
|
|
|
|
return (
|
|
<div className="relative flex h-full flex-col overflow-hidden bg-background text-foreground">
|
|
<main className="relative z-10 flex flex-1 flex-col overflow-hidden">
|
|
{route === 'welcome' && <Welcome />}
|
|
{route === 'progress' && <Progress bootstrap={bootstrap} />}
|
|
{route === 'success' && <Success />}
|
|
{route === 'failure' && <Failure bootstrap={bootstrap} />}
|
|
</main>
|
|
</div>
|
|
)
|
|
}
|