Skip to content

Fix #54: Fix comment handling after the first one#55

Merged
max-tet merged 1 commit intomainfrom
clayde/issue-54-fix-comment-visibility
Mar 25, 2026
Merged

Fix #54: Fix comment handling after the first one#55
max-tet merged 1 commit intomainfrom
clayde/issue-54-fix-comment-visibility

Conversation

@ClaydeCode
Copy link
Copy Markdown
Owner

Closes #54

Removed the two update_issue_state(INTERRUPTED) calls from run_update in tasks/plan.py. On failure (usage limit, timeout, or parse error), the function now just returns without changing state, so the issue stays in AWAITING_*_APPROVAL and the next tick naturally retries the update with the same new comments. Updated the corresponding test to assert that update_issue_state is NOT called on failure.

When plan update fails (usage limit, timeout, or parse error), the issue
should stay in AWAITING_*_APPROVAL so the next tick naturally retries
run_update with the same new comments. Previously, it set status to
INTERRUPTED which caused the orchestrator to retry with run_preliminary
(a full re-plan), dropping any comments seen since the plan was posted.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ClaydeCode ClaydeCode requested a review from max-tet March 25, 2026 06:42
@max-tet max-tet merged commit 6684878 into main Mar 25, 2026
2 checks passed
@max-tet max-tet deleted the clayde/issue-54-fix-comment-visibility branch March 25, 2026 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix comment handling after the first one

2 participants