Codex-Co-Engineer 3.4.0
Repository-side GitHub Release body for Codex-Co-Engineer 3.4.0.
A clearer Co-Engineer experience
3.4.0 gives Codex a visible team of external co-engineers while preserving a
simple contract: up to eight isolated assignments, one bounded submission,
one coordinated wait, and one verified decision. The plugin page, README,
skills, inline cards, accessibility states, wordmark, and final static artwork
now use the same language:
- Delegating to Co-Engineer
- Chatting with Co-Engineer
- Using Grok Co-Engineer
- Using Cursor Co-Engineer
- Using Muse Co-Engineer
Codex remains chief engineer. External workers operate on their own branches
and managed worktrees. Worker commits and draft PRs are evidence; they do not
silently become accepted product changes.
Luna-first, interrupt-driven coordination
Luna Max can serve as the low-cost relay and control layer. It receives typed
task-to-task events, maintains delivery and acknowledgement cursors, and wakes
Sol only for meaningful boundaries such as completed, blocked, failed,
question, timeout, user update, or merge-ready. Attempt and generation fences
prevent a late worker or replaced Luna task from settling the current run.
Sol High/XHigh remains the exception layer and regular-merge authority. A
merge requires the expected and current branch head/tree, fresh green checks,
accepted verifier evidence, and safe topology. Provider prose and thread
messages cannot override those facts.
Less context, better evidence
- Deterministic reducers aggregate typed receipts without replaying every
worker transcript through another model. UsageLedgerV1records provider-reported tokens, host-visible model bytes,
evidence bytes, invocations, waits, attention rounds, retries, and unknowns
separately.- Progressive lane health exposes provider, branch, head, and state first;
large diffs and logs remain retrievable by reference. - The PR-ready final card reports exact blockers or a verified
ready_for_sol_mergeresult. - Cleanup planning revalidates task/worktree/lock/ref identity and uses
expected-SHA compare-and-swap semantics before any deletion.
Truthful attention and compatibility
Grok questions that cannot enter the structured question channel no longer
project as successful work. They remain unresolved attention with bounded
question evidence. The five MCP tools remain status, delegate, task,
tasks, and cancel; omitting additive run fields preserves the 3.2.1
single-task path.
Validation
The release candidate is accepted only after the repository-owned exact-tree
gate, current GitHub CI, package inventory, and identity checks pass. The full
integrated feature candidate passed 2,079/2,079 tests before the version-only
release commit was formed.
Maintainer publication
After the exact candidate is reviewed, replace EXACT_REVIEWED_MAIN_SHA with
that immutable commit and verify it before publishing:
test "$(git rev-parse HEAD)" = "EXACT_REVIEWED_MAIN_SHA"
gh release create v3.4.0 \
--target EXACT_REVIEWED_MAIN_SHA \
--title "Codex-Co-Engineer 3.4.0" \
--notes-file docs/releases/v3.4.0.mdThis document does not independently authorize tagging, pushing, or release
publication.