codex-worker

Orchestrate parallel Codex CLI agents in git worktrees and tmux sessions.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Arist12/kimi-cli --skill codex-worker-arist12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-worker
Source: https://github.com/Arist12/kimi-cli/tree/main/.agents/skills/codex-worker
Command: npx skills add https://github.com/Arist12/kimi-cli --skill codex-worker-arist12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multiple Codex CLI agents running in parallel to tackle large tasks by dividing work into independent subtasks and running them concurrently.

Core Features & Use Cases

  • Orchestrates multiple Codex CLI agents, each in its own git worktree and tmux session.
  • Enables parallel triage, modular refactoring, and cross-file fixes by spawning dedicated workers for each subtask.
  • Replaces single-threaded task execution to speed up complex workflows when Codex and tmux are available.

Quick Start

Spawn a codex worker for each subtask by creating worktrees and tmux sessions, then feed prompts to each worker.

Frequently Asked Questions about codex-worker

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

FAQPage Schema
How do I run parallel Codex agents to speed up large refactoring tasks?

To run parallel Codex agents for large refactoring tasks, you spawn a dedicated worker for each subtask by creating individual git worktrees and named tmux sessions. This isolates concurrent execution and accelerates complex workflows.

Can I use tmux and git worktrees to triage issues across multiple packages simultaneously?

Yes, you can use tmux and git worktrees to triage issues across packages simultaneously. The approach distributes independent subtasks across multiple workers, enabling parallel triage and cross-file fixes without single-threaded execution bottlenecks.

What do I need to set up before spawning parallel Codex workers?

Before spawning parallel Codex workers, you need the Codex CLI and tmux installed. You also need an existing Git repository with the ability to create git worktrees and named tmux sessions to isolate each worker.

When should I use parallel Codex agents instead of a single agent?

You should use parallel Codex agents instead of a single agent when your work can be decomposed into independent subtasks. This includes modular refactors, lint fixes across packages, and issue triage, replacing single-threaded execution to speed up completion.

Does parallel task management with Codex agents require dependencies beyond tmux and git?

Parallel task management with Codex agents requires the Codex CLI, tmux, and a Git repository. It relies on creating git worktrees and named tmux sessions to manage the workers, but has no other external dependencies.

Why use git worktrees when orchestrating multiple Codex agents in tmux?

Git worktrees are used when orchestrating multiple Codex agents to provide each parallel worker with an isolated working directory. This prevents file conflicts during concurrent modular refactors and cross-file fixes within the same repository.