Summary
Tokenjuice's OpenClaw/Codex integration still silently produces no fresh artifacts on a current stable Viernes/OpenClaw installation, despite Tokenjuice reporting healthy hooks and rule validation.
This looks primarily like an OpenClaw core release/integration gap rather than a reducer failure, but I am opening it here because the Tokenjuice plugin gives a clean bill of health while capture is inactive.
Environment
- OpenClaw:
2026.7.1-2 (0790d9f)
@openclaw/tokenjuice: 2026.7.1- Tokenjuice core:
0.8.1
- Runtime: Codex native/app-server tool calls
Observed behavior
tokenjuice verify succeeds: 183 rules validated.tokenjuice doctor codex reports hooks healthy and configured.- The plugin is loaded by OpenClaw.
- The artifact audit sees 5,536 metadata files, but the latest production artifact remains
2026-06-21T16:40:41.749Z (now about 29 days old).
- Repeated live Codex-native exec/tool calls through the gateway do not create a newer
.meta.json artifact.
So the historical stats are valid, but current activity is not being captured. This failure is silent: normal plugin/Tokenjuice checks do not identify it.
Related OpenClaw work
This appears to be the runtime path tracked in openclaw/openclaw#95597: Codex native post_tool_use skipped agentToolResultMiddleware, which Tokenjuice uses.
The associated OpenClaw fix, openclaw/openclaw#108105, merged on July 15, 2026. However, the installed stable 2026.7.1-2 still does not relay native Codex results to Tokenjuice, so the fix does not appear to be present in this release.
Direct Tokenjuice reduction/storage and direct middleware invocation do create artifacts, which further points to the OpenClaw native relay rather than Tokenjuice's artifact store or reducers.
Questions / requested improvement
- Is the expected remediation simply the next OpenClaw stable release containing the relay change?
- Can the Tokenjuice OpenClaw integration detect this state and emit a warning when its Codex middleware is registered but no native results are arriving? A green
doctor plus weeks-stale artifacts is misleading.
- Is there a supported temporary workaround other than moving to an OpenClaw build that includes the core relay fix?
Happy to provide additional sanitized diagnostics or test a release candidate.
Summary
Tokenjuice's OpenClaw/Codex integration still silently produces no fresh artifacts on a current stable Viernes/OpenClaw installation, despite Tokenjuice reporting healthy hooks and rule validation.
This looks primarily like an OpenClaw core release/integration gap rather than a reducer failure, but I am opening it here because the Tokenjuice plugin gives a clean bill of health while capture is inactive.
Environment
2026.7.1-2(0790d9f)@openclaw/tokenjuice:2026.7.10.8.1Observed behavior
tokenjuice verifysucceeds:183 rules validated.tokenjuice doctor codexreports hooks healthy and configured.2026-06-21T16:40:41.749Z(now about 29 days old)..meta.jsonartifact.So the historical stats are valid, but current activity is not being captured. This failure is silent: normal plugin/Tokenjuice checks do not identify it.
Related OpenClaw work
This appears to be the runtime path tracked in openclaw/openclaw#95597: Codex native
post_tool_useskippedagentToolResultMiddleware, which Tokenjuice uses.The associated OpenClaw fix, openclaw/openclaw#108105, merged on July 15, 2026. However, the installed stable
2026.7.1-2still does not relay native Codex results to Tokenjuice, so the fix does not appear to be present in this release.Direct Tokenjuice reduction/storage and direct middleware invocation do create artifacts, which further points to the OpenClaw native relay rather than Tokenjuice's artifact store or reducers.
Questions / requested improvement
doctorplus weeks-stale artifacts is misleading.Happy to provide additional sanitized diagnostics or test a release candidate.