Repository navigation
·
1 commit
to main
since this release
A patch release: the Codex monitor's per-task timer no longer restarts after a halt. This page covers what changed since 0.14.2 (PR #152).
Task timers survive a resume
Each time a halted task was resumed, the runner reset its start time, so the monitor's timer went back to 0:00. A task worked for 40 minutes across a few halts could show 5.
- Active time carries over. The timer column shows the time the task has actually been running, summed across invocations. A halt still stops it; a resume continues from where it stopped.
- Wall-clock alongside. Once a task has been resumed, the time since its first start appears in parentheses:
7:00 (60:00)is 7 minutes of work over an hour that included waiting on halts. - run.json: each task gains
first_started_atandactive_secs. Older run files without them display as before. A segment that ended without a recorded end time (the process died mid-task) adds nothing.
Codex
No hooks/hooks.json change since 0.14.2, 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@forgeRestart the session to apply. On Codex: codex plugin marketplace add forcetrainer/forge --ref forge--v0.14.3, then codex plugin add forge@forge.