remote-codex-workers

Automate provisioning and maintenance of S3-backed remote Codex worker hosts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complex, manual work of provisioning and maintaining S3-backed remote Codex worker hosts, removing the need to manually manage orchestrator threads, slot workers, heartbeats, and S3 job queue state.

Core Features & Use Cases

  • Remote Worker Pool Configuration: Opt Codex hosts into shared S3-only worker pools, customize slot counts, intervals, lease durations, and bucket/prefix settings.
  • Automated Orchestration & Maintenance: Set up self-managing orchestrator and slot threads with heartbeat automations, exponential backoff logic, and compliant job lease management.
  • Use Case: Engineering teams running Codex at scale can use this Skill to quickly provision consistent worker capacity across multiple hosts, ensuring reliable job processing and full fleet status visibility without manual infrastructure management.

Quick Start

Use the remote-codex-workers skill to opt your current Codex host into the default remote worker pool with 4 worker slots.

Frequently Asked Questions about remote-codex-workers

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

FAQPage Schema
How do I configure an S3-backed remote Codex worker pool?

You can configure an S3-backed remote Codex worker pool by opting Codex hosts into a shared S3-only setup, customizing slot counts, intervals, lease durations, and bucket/prefix settings to enable self-managing job processing.

What is the best way to automate Codex worker orchestration and heartbeat management?

Automating Codex worker orchestration involves setting up self-managing orchestrator and slot threads with heartbeat automations, exponential backoff logic, and compliant job lease management to ensure reliable remote job processing.

Can I run scalable Codex worker fleets without manual infrastructure management?

Yes, you can provision consistent worker capacity across multiple hosts using automated S3 state management and fleet status reporting, ensuring reliable job processing without manual infrastructure maintenance.

Does the remote worker pool setup support idempotent job submission and lease protocols?

The remote worker pool setup adheres to stable idempotent job submission, lease, and heartbeat protocols, ensuring S3 state management and automated slot thread setup remain compliant with Pear API remote job queue systems.

Why do I need S3 state management for remote Codex worker pools?

S3 state management is needed to maintain reliable job queue infrastructure, enabling automated orchestrator threads and slot workers to process jobs consistently across distributed Codex hosts without manual state tracking.

Are there limitations when using S3-only worker pools for Codex orchestration?

S3-only worker pools require stable idempotent job submission and heartbeat protocols to function correctly, meaning environments lacking compliant lease management may experience inconsistent fleet status reporting and job processing delays.