claude-code - 💡(How to fix) Fix Regression: mid-task new instructions silently replace the original task instead of being treated as additive [2 comments, 3 participants]

TL;DR

Modify the Claude Code to classify new user messages during active tasks into append, amend, replace, or parallel categories and confirm before discarding the in-flight task.

Guidance

• Review the task management logic in the Claude Code to identify where the regression occurred between versions 4.5/4.6 and 4.7.
• Implement a message classification system to determine the intent of new user messages during active tasks, using the suggested categories: append, amend, replace, or parallel.
• Develop a confirmation mechanism to briefly ask the user before discarding the in-flight task when the classification is ambiguous.
• Test the updated logic with various user message scenarios to ensure the desired behavior is achieved.

Example

def classify_message(message, active_task):
    # Simplified example, actual implementation may vary
    if message.startswith("continue") or message.startswith("add"):
        return "append"
    elif message.startswith("replace") or message.startswith("new"):
        return "replace"
    # ... implement other categories and logic
    return "ambiguous"

def handle_user_message(message, active_task):
    classification = classify_message(message, active_task)
    if classification == "ambiguous":
        # Confirm with the user before discarding the task
        confirmation = input("Do you want to discard the current task? (yes/no)")
        if confirmation.lower() == "yes":
            # Discard the task and start a new one
            pass
        else:
            # Merge the new message into the active task
            pass
    # ... handle other classifications

Notes

The provided example is a simplified illustration and may not cover all edge cases. The actual implementation should consider the specific requirements and constraints of the Claude Code and its task management logic.

Recommendation

Apply a workaround by modifying the task management logic to include the suggested message classification and confirmation mechanism, as the issue is specific to the current version (Opus 4