codex-issue-runner

Automate Codex CLI agents in isolated iTerm slots for GitHub issues.

1|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/aj47/agent-skills --skill codex-issue-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-issue-runner
Source: https://github.com/aj47/agent-skills/tree/main/codex-issue-runner
Command: npx skills add https://github.com/aj47/agent-skills --skill codex-issue-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates spinning up OpenAI Codex CLI agents in isolated iTerm slots to work on GitHub issues and PRs, enabling parallel, context-aware code exploration and task execution across multiple workspaces.

Core Features & Use Cases

  • Slot-based Codex agents: Each slot is an independent workspace that can run one Codex agent at a time.
  • Context-aware task execution: Codex reads full issue/PR context via gh to understand objectives before making changes.
  • Deterministic workflow guidance: Clear steps to identify available slots, prepare slots, launch Codex, submit the task, and verify output.

Quick Start

Create a Codex agent for a specific issue number and ensure it reads the issue context before acting.

Frequently Asked Questions about codex-issue-runner

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

FAQPage Schema
How do I automate running Codex CLI agents on GitHub issues in parallel?

You can automate Codex CLI agents by spinning up isolated iTerm slots, where each slot independently reads GitHub issue context via gh commands and executes code tasks with up to five parallel agents.

What is the best way to manage multiple OpenAI Codex agents working on different GitHub issues?

Managing multiple Codex agents is best handled through a slot-based execution model that isolates each agent in an independent iTerm workspace, ensuring context-aware task execution and deterministic output verification.

How do I ensure Codex reads GitHub issue context before submitting code changes?

To ensure Codex reads issue context, the workflow specifies preparing each iTerm slot and using gh commands to fetch full issue or PR details before launching the Codex agent to act on the task.

Can I run more than five Codex agents at the same time using terminal slots?

No, the slot-constrained execution model supports up to five parallel Codex agents, limiting simultaneous task execution to maintain safe and deterministic workflows across isolated iTerm slots.

Do I need the GitHub CLI to use Codex agents for resolving repository issues?

Yes, the GitHub CLI is required because the Codex agents rely on gh commands to read full issue and PR context, enabling context-aware code exploration and task execution within the terminal.