claude-code - 💡(How to fix) Fix /clear orphans background tasks by modifying session state in place [2 comments, 3 participants]

TL;DR

The issue can be addressed by either tearing down orphaned tasks when /clear is called or surfacing them to the new conversation.

Guidance

• To fix the issue, consider modifying the /clear command to either stop all background tasks started in the previous conversation or to pass their task_ids to the new conversation.
• Verify the fix by running the repro steps and checking if the background tasks are properly stopped or if their task_ids are correctly listed in the new conversation.
• To mitigate the issue, users can currently use OS-level commands like ps and kill to manage the tasks, but this requires knowledge of the PIDs.
• Consider adding a <background-tasks> system reminder to list inherited task_ids and descriptions, making it easier for the model to discover and manage the tasks.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The suggested fix requires changes to how the /clear command handles background tasks, which may have implications for the overall design of the system.

Recommendation

Apply a workaround by surfacing orphaned tasks to the new conversation, as this seems to be a more feasible and less disruptive solution compared to tearing down the tasks. This approach allows for better task management and visibility.