EVO Code Host

EVO-Code-host

Always-on headless host service for EVO Code clients.

Related Repositories

• App repo (EVO-Code): https://github.com/0xdippo/EVO-Code
• Host repo (EVO-Code-host, this repo): https://github.com/0xdippo/EVO-Code-host

What this provides

• Rust + Axum daemon (evo-code-host) suitable for 24/7 running.
• Token-authenticated HTTP API and WebSocket endpoint.
• Config-driven allowed repository roots.
• Embedded browser UI served from the same host process.
• Health endpoints: /healthz and /readyz.
• macOS launchd scripts for auto-start and auto-restart.

Browser + App clients

One host process now serves both:

• Desktop app clients (existing remote mode) via /api/* + /ws
• Browser clients via / (works on any modern browser-capable device: iPad, tablets, laptops, desktop browsers)

No separate UI server is required.

Build prerequisites

Host builds require:

• Rust toolchain
• Node.js + npm (used by build.rs to build web/dist when stale or missing)

Config

Copy `config/config.example.toml` to `~/.config/evo-code-host/config.toml` and set:

• listen_addr: usually 0.0.0.0:7700
• service_token: shared token used by app/browser clients
• allowed_repo_roots: list of absolute roots this service can operate on

Run locally

cargo run

`cargo` will trigger the web UI build automatically when required.

The service reads config from:

• $EVO_CODE_HOST_CONFIG if set
• otherwise ~/.config/evo-code-host/config.toml

macOS launchd

./ops/launchd/install.sh
./ops/launchd/status.sh
./ops/launchd/uninstall.sh

API compatibility

Implemented:

• /api/list_shared_repositories
• /api/open_repository
• /api/write_repository_file
• /api/setup_project
• /api/create_plan_run
• /api/save_plan
• /api/approve_plan
• /api/reject_plan
• /api/start_run
• /api/cancel_run
• /api/list_changed_files
• /api/load_changed_file_diff
• /api/apply_review_decision
• `/api/clear_accepted_