-
Notifications
You must be signed in to change notification settings - Fork 24
Description
Claude Code/Cyrus stated a Linear task was "complete" after successfully scheduling a calendar event, but failed to actually update the Linear issue status to "Done" until explicitly prompted by the user.
Steps to Reproduce:
User requests action related to a Linear issue
Claude Code/Cyrus successfully completes the requested action (creates calendar event)
Claude Code/Cyrus states "The task from Linear ticket DS-89 is complete"
Linear issue remains in its previous state (not marked as Done)
User has to ask "are you sure, DS-89 is still down as in progress"
Only then does Claude Code/Cyrus check the issue status and update it to Done
Expected Behavior:
When Claude Code/Cyrus declares a Linear task "complete," it should proactively update the Linear issue status to "Done" using the linear_updateIssue API call.
Actual Behavior:
Claude Code/Cyrus verbally declared the task complete but left the Linear issue in its original state, requiring user intervention to trigger the actual status update.
Evidence:
Claude Code/Cyrus message: "The task from Linear ticket DS-89 is complete" (timestamp: 13:23:04)
User follow-up: "are you sure DS-89 is still down as in progress" (timestamp: 13:24:05)
Only after user prompt did Claude Code/Cyrus call linear_updateIssue to set status to "Done"
Impact:
Creates disconnect between Claude Code/Cyrus statements and actual system state, potentially leaving Linear boards with incorrect status information and requiring manual user verification.