remote-codex-orchestrator

Automate maintenance of S3-backed remote Codex worker fleets.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill remote-codex-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remote-codex-orchestrator
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/remote-codex-orchestrator
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill remote-codex-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually maintaining distributed remote Codex worker fleets is time-consuming and error-prone, requiring constant tracking of slot health, automation schedules, job status, and S3-based state across multiple hosts. This skill eliminates that manual overhead by automating all routine orchestrator maintenance tasks.

Core Features & Use Cases

  • Adaptive Orchestrator Heartbeat: Manages exponential no-change backoff for the orchestrator thread, reducing unnecessary runs while staying responsive to fleet changes.
  • Slot Lifecycle Automation: Automatically creates, repairs, and refreshes worker slot threads with correct project placement and self-managing heartbeat automations.
  • Fleet & Task Diagnostics: Publishes machine-readable fleet status and cursor-based task logs from S3 for full visibility into worker health and job execution. Use Case: For teams running remote Codex worker pools to process background API jobs or automated tasks, this skill ensures all slots are healthy, automations are up to date, and you have real-time visibility into fleet performance without manual intervention.

Quick Start

Use the remote-codex-orchestrator skill to run a full maintenance cycle for your configured remote Codex worker host, including slot health checks, automation refreshes, and fleet status reporting.

Frequently Asked Questions about remote-codex-orchestrator

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

FAQPage Schema
How do I automate remote Codex worker fleet maintenance?

Automate remote Codex worker fleet maintenance by running a full maintenance cycle that checks slot health, refreshes automations, and reports fleet status using S3-backed state persistence. This eliminates manual tracking of orchestrator health and job execution.

How does orchestrator heartbeat automation handle idle periods?

Orchestrator heartbeat automation uses exponential no-change backoff to reduce unnecessary runs during idle periods while staying responsive to fleet changes. This adaptive scheduling ensures efficient resource usage without missing critical updates.

How do I track remote Codex worker slot health across multiple hosts?

Track remote Codex worker slot health across multiple hosts through automated fleet status reporting and cursor-based task logs delivered from S3. This provides full visibility into worker health and job execution without manual intervention.

Can I use S3 state persistence for distributed Codex worker pools?

Yes, S3 state persistence supports distributed Codex worker pools by maintaining orchestrator and slot component state. This enables consistent slot availability and cursor-based task log delivery across all hosts in the fleet.

What is the best way to repair stale automations in a Codex worker fleet?

The best way to repair stale automations in a Codex worker fleet is through automated slot lifecycle management that creates, repairs, and refreshes worker slot threads with correct project placement and self-managing heartbeat automations.

Why does my remote Codex orchestrator require manual slot tracking?

Remote Codex orchestrators require manual slot tracking when lacking automated lifecycle management. This skill eliminates that overhead by automatically managing slot threads, heartbeat automations, and stale automation repair across the entire fleet.