Offload Rust builds to remote workers for faster compilation in multi-agent workflows.
What Is RCH?
RCH (Remote Compilation Helper) transparently intercepts cargo commands and routes them to powerful remote build servers. Your local machine stays responsive while heavy Rust compilations run elsewhere.
When running multiple AI agents that all trigger builds, your local CPU becomes a bottleneck. RCH solves this by syncing source to remote workers, building there, and streaming artifacts back.
Remote Workers
Build on powerful remote servers
Transparent
Works via Claude Code hook
Fast Sync
rsync + zstd compression
Worker Pool
Priority-based scheduling
How It Works
RCH intercepts cargo commands via a Claude Code hook and offloads them to remote workers.
# Local: You run cargo buildcargo build --release↓# RCH Hook intercepts the command↓# Source synced to worker via rsync↓# Remote: Build runs on powerful server↓# Artifacts synced back to local machine
Quick Start
Get started with these essential commands.
Worker Management
RCH supports multiple remote workers with priority-based scheduling.
# Workers are stored in ~/.config/rch/workers.toml[[workers]]name = "build-server-1"host = "ubuntu@192.168.1.100"slots = 48priority = 100tags = ["fast", "baremetal"][[workers]]name = "build-server-2"host = "ubuntu@192.168.1.101"slots = 16priority = 80tags = ["secondary"]
Diagnostics
RCH includes comprehensive diagnostics to troubleshoot issues.
rch doctor if builds aren't being offloaded. It checks prerequisites, configuration, and worker connectivity.Configuration
RCH configuration lives in ~/.config/rch/.
# View current configrch config show# Set default workerrch config set default_worker=build-server-1# Update RCH binaries on all workersrch update --remote
rch update --remote after updating the local RCH binary.Tool Integration
RCH integrates seamlessly with other flywheel tools.
RCH + NTM
Agents spawned by NTM automatically use RCH for their builds. Multiple agents can compile in parallel without overwhelming local CPU.
RCH + RU
RU syncs repos that RCH then builds remotely. Use ru sync to update sources, then build with RCH-accelerated cargo.
RCH + Beads
Track build-related tasks via beads. Create issues for build failures or optimization opportunities.
Best Practices
Get the most out of RCH with these recommendations.
Set up passwordless SSH access
Use servers with many CPU cores
Update workers with rch update --remote
Check rch status regularly