forge 0.14.2

A patch release: on Claude Code, the orchestrator now tells you what's going on during a run, and stalled agents get noticed. This page covers what changed since 0.14.1 (PR #151).

A status line every 10 minutes (Claude)

Between agent notifications the Claude orchestrator was silent, so a long-running worker and a stuck one looked the same, and finding out meant asking.

• When execution starts, the orchestrator arms a 10-minute heartbeat. Each tick prints one line, for example:
  ⏱ 14:20 · Task 3/8 · worker (forge-standard) · running 14m · 12:41 "running touched tests" (2m ago) · tasks 1–2 passed
• Workers and reviewers append one line per step to a progress file, which is where the "what is it doing" part comes from.
• The heartbeat stops when the run passes, halts or reaches close-out.

Stalled agents get noticed (#146)

A worker that started its suite in the background and ended its turn could sit idle indefinitely. One did for about 24 minutes on a recent run, and nobody noticed until the user asked.

• Prevention: agents never end a turn while a command they started is still running. A command longer than the 10-minute foreground limit runs in the background and writes an exit marker, and the agent waits for that marker within its own turn.
• Detection: if a tick finds an agent that has gone idle without reporting, the status line names it and the orchestrator nudges it once. Nothing is counted across ticks.

Codex is unaffected: codex exec has no background mode, and forge-monitor.py already shows progress there.

Codex

No hooks/hooks.json change since 0.14.1, so Codex doesn't ask you to re-trust forge's hooks.

Install

claude plugin marketplace update forge
claude plugin update forge@forge        # or: claude plugin install forge@forge

Restart the session to apply. On Codex: codex plugin marketplace add forcetrainer/forge --ref forge--v0.14.2, then codex plugin add forge@forge.