From 2a24377870fa7e9ac67e0cb3c8af87447c043a94 Mon Sep 17 00:00:00 2001 From: Shirone Date: Sun, 25 Jan 2026 13:42:07 +0100 Subject: [PATCH] fix: Clear planSpec.currentTaskId instead of feature.currentTaskId in resetStuckFeatures Address CodeRabbit review comment: The reset logic was incorrectly clearing feature.currentTaskId (which doesn't exist on Feature type) instead of feature.planSpec.currentTaskId. This left planSpec.currentTaskId stale, causing UI/recovery to still point at reverted tasks. Co-Authored-By: Claude Opus 4.5 --- apps/server/src/services/auto-mode-service.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/server/src/services/auto-mode-service.ts b/apps/server/src/services/auto-mode-service.ts index 28ca230d..de2522f5 100644 --- a/apps/server/src/services/auto-mode-service.ts +++ b/apps/server/src/services/auto-mode-service.ts @@ -553,10 +553,10 @@ export class AutoModeService { `[resetStuckFeatures] Reset task ${task.id} for feature ${feature.id} from in_progress to pending` ); // Clear currentTaskId if it points to this reverted task - if (feature.currentTaskId === task.id) { - feature.currentTaskId = undefined; + if (feature.planSpec?.currentTaskId === task.id) { + feature.planSpec.currentTaskId = undefined; logger.info( - `[resetStuckFeatures] Cleared currentTaskId for feature ${feature.id} (was pointing to reverted task ${task.id})` + `[resetStuckFeatures] Cleared planSpec.currentTaskId for feature ${feature.id} (was pointing to reverted task ${task.id})` ); } }