restart-rustclaw

Rebuild RustClaw and restart launchd-managed agents with a rolling delay.

5|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/tonitangpotato/rustclaw --skill restart-rustclaw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: restart-rustclaw
Source: https://github.com/tonitangpotato/rustclaw/tree/main/skills/restart-rustclaw
Command: npx skills add https://github.com/tonitangpotato/rustclaw --skill restart-rustclaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates rebuilding RustClaw and performing a rolling restart of the three launchd-managed agent instances (main, agent2, marketing) to apply new binaries without downtime.

Core Features & Use Cases

  • Automates cargo build and rolling restart across all three RustClaw agents.
  • Coordinates sequential restarts with a configurable delay to avoid shared resource conflicts.
  • Verifies the new binary exists and restarts each agent to ensure a live deployment after changes.

Quick Start

Run the rolling restart script to rebuild RustClaw and restart all three launchd-managed agents.

Frequently Asked Questions about restart-rustclaw

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

FAQPage Schema
How do I automate a rolling restart for launchd-managed Rust agents?

A rolling restart sequentially reboots multiple launchd-managed agent instances with a brief delay between each to avoid shared resource conflicts. It ensures new binaries are applied seamlessly without downtime across main, agent2, and marketing deployments.

How do I rebuild a Rust application and restart multiple launchd agents without downtime?

To rebuild and restart without downtime, run a cargo build to compile the new binary, verify it exists, and sequentially restart each launchd-managed agent instance with a brief delay between reboots to avoid shared resource conflicts.

Do I need a specific macOS environment to perform a rolling restart of RustClaw agents?

Yes, performing a rolling restart of RustClaw agents requires a functioning RustClaw source tree and access to the macOS launchd workflow. This environment allows you to validate the newly built binary and seamlessly coordinate sequential restarts.

Can I use cargo build to coordinate upgrades across multiple Rust agent deployments?

Yes, you can use cargo build to compile source changes and coordinate upgrades across multiple Rust agent deployments. The process validates the new binary before sequentially restarting main, agent2, and marketing instances to ensure a live deployment.

Why does a rolling restart include a delay between restarting launchd agents?

A rolling restart includes a brief delay between restarting launchd agents to avoid shared resource conflicts. Coordinating sequential restarts ensures the system remains stable while applying new binaries across main, agent2, and marketing deployments.