From 23c75578c01b1e258711eece5621f0a85b2ad21f Mon Sep 17 00:00:00 2001 From: arkon Date: Thu, 22 Jan 2026 20:52:41 +0100 Subject: [PATCH] fix: persist respawnEnabled state to state.json The respawn controller's enabled/disabled state was not being saved, so CLI status couldn't show whether respawn was active. Co-Authored-By: Claude Opus 4.5 --- src/types.ts | 2 ++ src/web/server.ts | 3 +++ 2 files changed, 5 insertions(+) diff --git a/src/types.ts b/src/types.ts index e42f7212..bdf3c2c2 100644 --- a/src/types.ts +++ b/src/types.ts @@ -74,6 +74,8 @@ export interface SessionState { inputTokens?: number; /** Output tokens used */ outputTokens?: number; + /** Whether respawn controller is currently enabled/running */ + respawnEnabled?: boolean; /** Respawn controller config (if enabled) */ respawnConfig?: RespawnConfig & { durationMinutes?: number }; /** Ralph / Todo tracker enabled */ diff --git a/src/web/server.ts b/src/web/server.ts index 795228db..ffd1f310 100644 --- a/src/web/server.ts +++ b/src/web/server.ts @@ -1289,6 +1289,9 @@ export class WebServer extends EventEmitter { ? Math.round((timerInfo.endAt - timerInfo.startedAt) / 60000) : undefined; state.respawnConfig = { ...config, durationMinutes }; + state.respawnEnabled = controller.state !== 'stopped'; + } else { + state.respawnEnabled = false; } this.store.setSession(session.id, state); }