personal-codex-worker

Delegates packet-scoped issues to unattended Codex workers launched from herdr panes in local clones.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kosako/agent-tools --skill personal-codex-worker-kosako
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: personal-codex-worker
Source: https://github.com/kosako/agent-tools/tree/main/shared/skills/personal-codex-worker
Command: npx skills add https://github.com/kosako/agent-tools --skill personal-codex-worker-kosako

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It lets a Claude orchestrator hand off a well-scoped implementation task to an unattended Codex CLI worker without giving that worker access to GitHub, the network, or the packet directory, while keeping authorization, completion detection, and PR creation under strict orchestrator control. ## Core Features & Use Cases - Sandboxed worker launch: Runs codex exec in a per-issue local clone via a herdr pane, using only the preflight-generated launch argv with connectors, MCP servers, and execpolicy rules disabled. - Deterministic completion and transcription: Detects completion through a nonce-stamped done file and result file, then transcribes the worker's final message into the packet only after it passes the public-safety gate. - Orchestrator-controlled PR flow: Fetches worker commits back into the main repository, verifies all trailers are Codex-only, then pushes and opens the PR without merging. - Use Case: You say "delegate packet #291 to Codex" and the skill clones the repo, launches the worker in a #291 herdr tab, waits for completion, records the result in the packet, and opens a trailer-checked PR. ## Quick Start Ask the orchestrator to delegate packet #N to Codex for implementation and wait for the worker to finish and the PR to be opened.

Frequently Asked Questions about personal-codex-worker

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

FAQPage Schema
How do I delegate a coding task to a Codex worker from Claude?▼

Issue an explicit instruction such as delegating packet #N to Codex. The skill clones the repository, runs the preflight check, writes a brief containing the packet's request verbatim, and launches codex exec in a herdr pane labeled with the issue number.

How does the Codex worker sandbox restrict file and network access?▼

The worker runs with workspace-write sandboxing inside its own local clone, with connectors, MCP servers, browser and computer use disabled. Only the clone's git directory is opened via the preflight's --add-dir flag; GitHub, network, and the packet directory stay inaccessible.

Can I launch a Codex worker from inside a Codex session?▼

No. The preflight detects CODEX_SANDBOX or CODEX_THREAD_ID and blocks the launch as asymmetric, since delegation is one-way from Claude to Codex. Hand the launch to Claude or a human instead of attempting nested codex exec.

What happens when the Codex worker hits a usage limit?▼

The skill stops with Blocked at: limit and never auto-restarts. It marks the packet blocked, records the stop reason, stashes staged, unstaged, and untracked changes into the run directory, and waits for a human to decide on resumption after the limit resets.

Why does the skill refuse to push a branch with mixed commit trailers?▼

PRs require all added commits to carry Codex-only Co-Authored-By trailers so author and reviewer routing stays valid. If any Claude trailer appears, the skill blocks the push and requires a new branch and new PR instead of mixing authors.

What are the limitations of this delegation approach?▼

It requires herdr running for unattended launch, otherwise it hands a run script to a human. It supports only one worker per orchestrator session, never merges PRs, and cannot detect workers started outside herdr except through packet launch records.