remote-codex-worker-slot

Process queued S3-backed Codex jobs with lease management and conflict avoidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the management of remote Codex worker slots to process queued S3-backed jobs reliably, eliminating manual work for lease management, queue polling, retry handling, and logging for distributed Codex task workflows.

Core Features & Use Cases

  • Automated Job Queue Processing: Claims and processes queued Codex jobs sequentially with built-in lease conflict avoidance to ensure only one worker processes a job at a time.
  • Resilient State Management: Handles lease renewal, stale lease reclamation, job timeouts, max attempt limits, and cancellation signals to prevent duplicate or failed work.
  • Adaptive Idle Backoff: Automatically adjusts worker heartbeat intervals based on queue empty states to reduce unnecessary S3 polling while remaining responsive to new work. Use Case: Teams running distributed Codex task queues can use this Skill to automate worker slot operations, ensuring jobs are processed reliably without manual intervention for lease or queue management.

Quick Start

Use the remote-codex-worker-slot skill to run one bounded repeat-until-empty worker wake cycle for your configured S3-backed Codex job queue.

Frequently Asked Questions about remote-codex-worker-slot

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

FAQPage Schema
How do I process S3-backed job queues with remote Codex workers?

S3-backed job queue processing with remote Codex workers is automated by claiming, executing, and completing jobs sequentially while respecting lease ownership rules and timeouts to prevent duplicate work.

What is lease management for distributed task queues?

Lease management for distributed task queues is a conflict avoidance mechanism ensuring only one worker processes a job at a time through lease renewal, stale lease reclamation, and cancellation signals.

How do I prevent duplicate job execution in S3 job queues?

Duplicate job execution in S3 job queues is prevented through built-in lease conflict avoidance, ensuring only one worker slot can claim and process a queued job at any given time.

Can I use adaptive idle backoff for S3 queue polling?

Adaptive idle backoff for S3 queue polling automatically adjusts worker heartbeat intervals based on queue empty states, reducing unnecessary polling while remaining responsive to new work.

How do I handle job timeouts and max attempt limits for queued Codex tasks?

Queued Codex task timeouts and max attempt limits are handled through resilient state management that processes cancellation signals and reclaims stale leases to prevent failed or duplicate work.

Does remote Codex worker orchestration support immutable logging?

Remote Codex worker orchestration supports immutable logging and terminal result publication, ensuring distributed task queue workflows maintain reliable processing records without manual intervention.