· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Six Ideas v0.4.0
Coordinate parallel Codex work
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Help my Codex tasks move in parallel with less duplicate work and fewer crossed edits
Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Keep parallel Codex tasks moving in one shared checkout without duplicate work or crossed edits. Codex Coordinator gives each task a visible, bounded lane, reuses related tasks before creating new ones, and stays lightweight—no background manager, polling loop, transcript store, extra worktrees, or required pull requests. An optional manual, read-only Doctor checks package compatibility and recommends update or reinstall when something is broken.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: codex-coordinator description: Keeps parallel Codex tasks in one shared Git checkout inside clear, visible boundaries. Uses a small local active-claim board and an optional user-invoked, goal-scoped Coordinator; it does not create background management, a heartbeat, scheduler, transcript store, or mandatory pull-request workflow. --- # Codex Coordinator Codex Coordinator is a task-boundary and visibility layer around native Codex tasks. Native Codex remains responsible for tasks, execution, messages, status, and transcripts. This skill records only the minimum metadata needed to avoid planned overlap. Supported project marker schema: `2`. A schema-1 enabled project is legacy state and must be migrated before coordinated writes. A disabled marker remains an opt-out and is not read further. ## Load only what the action needs - Starting, joining, splitting, claiming, completing, or integrating work: read [references/operations.md](references/operations.md), then [references/execution.md](references/execution.md). - Sending or acting on a peer collision or dependency notice: also read [references/messaging.md](references/messaging.md). - Enabling, disabling, installing, or onboarding: read [references/installation.md](references/installation.md). - Recovering a stale or interrupted claim: read [references/recovery.md](references/recovery.md). - Updating, removing, or changing Coordinator itself: read [references/maintenance.md](references/maintenance.md). - Checking whether the installed package can load: read [references/doctor.md](references/doctor.md). Read each selected file completely. Do not load every lane for ordinary work. ## Enablement 1. Resolve the Git common repository and primary worktree. 2. Read `.codex/coordination/project.yaml` before any other Coordinator state. 3. `coordination_enabled: false` is an explicit opt-out. Continue normally and read no board records. 4. `coordination_enabled: true` with schema 2 enables the board. It does not automatically create, pin, wake, or retain a Coordinator task. The user may explicitly designate one normal task as the Coordinator for one goal. 5. When the marker is absent, initialise only after a direct request to enable Coordinator, an explicit `$codex-coordinator` request for real parallel work, or the repository guidance's verified active-task trigger. Otherwise create nothing. 6. A global installation alone manages no repository. ## Core invariants - Default to one native Codex task. Create durable task windows only when the user explicitly asks for decomposition or a Coordinator and the work has two or three substantial, complete verticals that can progress with little coordination chatter. - Three active durable tasks is the normal maximum. Going above three requires a direct user decision recorded by the claiming task. Twelve is the hard board limit. - An explicitly requested Coordinator is one normal, goal-scoped task. It gives each durable task a complete goal and visible work boundary, remains available when the user invokes it again, and ends when the goal ends. It is not automatically created and does not become permanent repository management. - The Coordinator claims the exclusive `goal-coordination` action. Its bounded claim goal is the shared goal shown in the generated `CURRENT.md`. It need not claim source paths unless it will edit them. - The Coordinator may assign two or three substantial verticals. A vertical includes the investigation, implementation, focused tests, and documentation needed for its bounded outcome; do not split routine commands, small reviews, or mechanical edits into separate windows. - Reuse before create. Before opening a durable task, the Coordinator checks for a suitable related local task in the same repository and primary checkout. Reuse it with one bounded `GOAL_ASSIGNMENT` when it is not busy with unrelated work or waiting on a user decision. Create a new local task only when no suitable task exists. - Every
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 10 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugins_6a5c8cb6a5648191a43a76e6a1e637d8
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.