Summary
The shipped memory-consolidation cron job invokes the claude CLI with flags the current Claude Code release rejects, so the job fails on every run.
Observed
{"level":"error","msg":"memory-consolidation failed","error":"Error: claude exited 1: Error processing --setting-sources: Invalid setting source: --system-prompt. Valid options are: user, project, local\n"}
(Claude Code 2.x — --setting-sources no longer accepts --system-prompt as a value; looks like a flag-ordering/quoting regression in the job command.)
Environment
Ubuntu 24.04, LifeOS v6.0.0, Claude Code current stable, Pulse via manage.sh.
Impact
Job fails every run; contributes (together with assistant-heartbeat, filed separately) to /healthz being permanently degraded on fresh installs.
Suggestion
Update the job's claude invocation to current CLI flags, and consider gating shipped cron jobs behind a config default that keeps /healthz honest-green on a fresh install.
Summary
The shipped
memory-consolidationcron job invokes theclaudeCLI with flags the current Claude Code release rejects, so the job fails on every run.Observed
(Claude Code 2.x —
--setting-sourcesno longer accepts--system-promptas a value; looks like a flag-ordering/quoting regression in the job command.)Environment
Ubuntu 24.04, LifeOS v6.0.0, Claude Code current stable, Pulse via manage.sh.
Impact
Job fails every run; contributes (together with assistant-heartbeat, filed separately) to
/healthzbeing permanently degraded on fresh installs.Suggestion
Update the job's claude invocation to current CLI flags, and consider gating shipped cron jobs behind a config default that keeps
/healthzhonest-green on a fresh install.