rch

Route Rust, Bun, and C/C++ compilation commands to remote SSH workers.

58|3|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Dicklesworthstone/remote_compilation_helper --skill rch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rch
Source: https://github.com/Dicklesworthstone/remote_compilation_helper/tree/main/.claude/skills/rch
Command: npx skills add https://github.com/Dicklesworthstone/remote_compilation_helper --skill rch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Remote compilation tasks are offloaded from the local machine to a fleet of remote workers to speed up builds.

Core Features & Use Cases

  • Transparent interception of common build commands (cargo, bun, gcc) and routing to remote workers.
  • Smart worker selection using availability, priority, and project locality to maximize throughput.
  • Project affinity and incremental builds to reuse cached assets and avoid redundant transfers.
  • Fail-open design: if remote execution fails, fall back to local builds to avoid blocking developers.
  • Use Case: When multiple AI coding agents or CI jobs trigger concurrent builds, RCH ensures fast, parallelized compilation without user intervention.

Quick Start

  • Start the daemon: rchd &
  • Create or edit ~/.config/rch/workers.toml with your worker definitions (id, host, user, key, total_slots)
  • Install Claude hook: rch hook install
  • Validate with: rch doctor

Frequently Asked Questions about rch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I offload Rust or Bun compilation to a remote worker?

You can offload builds by running the rchd daemon, defining remote hosts in a workers.toml configuration file, and installing the Claude hook to intercept and route compilation commands to those remote workers.

How does remote build offloading handle concurrent compilation from multiple AI agents?

It uses smart worker selection based on availability, priority, and project locality to maximize throughput. This ensures multiple AI coding agents or CI jobs can trigger concurrent builds that are parallelized across the worker fleet.

Do I need Docker to run remote builds over SSH?

No, Docker is not required. The system specifically supports Dockerless SSH-based execution, allowing you to route and execute compilation commands directly on remote workers over SSH without containerization.

What happens if a remote build fails or the worker becomes unavailable?

The system uses a fail-open design, meaning if remote execution fails, it automatically falls back to local builds. This ensures developers and AI agents are never blocked by remote worker unavailability or execution errors.

How do remote builds reuse cached assets to avoid redundant file transfers?

The system uses project affinity and incremental builds to reuse cached assets. By selecting workers based on project locality, it ensures that previously compiled assets on the remote worker are reused, avoiding redundant file transfers.

How do I validate my remote worker configuration and setup?

You can validate your setup by running the `rch doctor` command. This checks that the rchd daemon is running, your workers.toml configuration is valid, and the Claude hook integration is correctly installed.