You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Foreman has a new icon: a green tag with a plumb line, from Foundry's
hallmark-seal identity. The README banner, wordmark and Codex plugin icon use
it. The Ember scene now ends with a stamp pressing that seal onto the answer,
and each README graphic carries the seal in a corner. No recorded text,
number or timing in the graphics changed.
Codex
After you update Foreman, review and trust its hooks again in /hooks.
Codex runs a hook only after you trust it. This update adds a hook on collaborationspawn_agent and adds Bash to the matcher of the decision
recall hook. Both change the hook registrations, so until you trust them
again, Codex does not run the new hook or the decision recall hook at all.
On Windows, each hook now starts Node from cmd instead of PowerShell. Each
command in the Codex shell starts two Foreman hooks. On the test machine,
those two hooks now take about 0.6 seconds less in total. When PATH has no
Node, the hooks still find it through a configured fnm default. This changes
the command of every Foreman hook. Until you trust the hooks again in /hooks, Codex runs none of them.
A subagent that carries a roadmap entry's handoff is now named foreman_<id>, for example foreman_042. When it stops, Foreman ties its
finish to that entry. With taskCloseGate set to "block", the session that
spawned it is blocked once from ending its turn while the entry is still planned or in_progress. An entry awaiting acceptance, or already closed,
passes. So does an entry whose last note line is paused: or review pending:, so each collaborationfollowup_task to a subagent whose
review is pending does not block the coordinator again. An explicit codex-task.js check still blocks once on such an entry.
A task_name that is foreman or starts with foreman_ is refused unless
it is exactly foreman_<id> for an entry in ROADMAP.jsonl. Every other
name passes, and a handoff spawned under another name runs normally, but its
finish is not tied to its entry.
A reviewed increment that is paused or gets no answer now records Codex session <session id> in its note. You can continue it from a new
process with codex exec resume <session id> -. The - makes Codex read
your decision from standard input, so the shell does not parse it. Type or
paste the decision, then end input with Ctrl+D in a POSIX shell or Ctrl+Z
and Enter in PowerShell or cmd. A new session that finds the note offers this
command before it crafts the work again.
When a command's output contains a [Foreman: <id>] anchor and the decision
documents folder has <id>.md, Foreman now tells the model to read that
document before it changes what the anchor governs. Codex reads files
through its shell, so this covers files it reads that way. One notice names
at most 20 decision documents and says how many it left out. Recorded
lessons are still recalled only when Codex uses apply_patch, Read, Edit
or Write on the file. Claude Code keeps decision recall on Read, Edit
and Write.