Describe the bug
A clear and concise description of what the bug is.

To Reproduce
List the steps to replicate the bug:

1. ...
2. ...
3. ...

Expected behavior
Describe what you expected to happen instead of the observed behavior.

Screenshots
If relevant, attach screenshots to illustrate the problem.

System Information (please complete the following information):

• Operating System: [e.g., macOS with M-series chip]
• Python Version: [e.g. v3.10]

Additional context
Include any extra details or related information that may help diagnose the issue.

Bug Title:

OML Agent fails to reconnect after network interruption on Windows (Dell Latitude)

Description :
When an OpenMind OML agent is running on Windows and the network connection is temporarily interrupted, the agent does not automatically reconnect after the network is restored. As a result, tasks remain stuck in a pending state until the agent is manually restarted.

Steps to Reproduce :
Start an OpenMind OML agent and confirm it is actively processing or waiting for tasks.

Disable the network connection (e.g., turn off Wi-Fi or unplug Ethernet) for 10–30 seconds.

Re-enable the network connection and submit a new task to the agent.
Expected Behavior
The agent should automatically detect the restored network connection and resume normal task processing without requiring a manual restart.

Actual Behavior:
The agent remains disconnected and unresponsive. Tasks stay queued or fail silently until the agent process is manually restarted.

System Information:
Device: Dell Latitude
Operating System: Windows Windows 11 pro version 23H2

Additional Context
No explicit error or warning is logged when the network connection is restored.
The issue occurs consistently after short network interruptions.
Restarting the agent immediately resolves the issue, indicating missing reconnection or retry logic.

Improved network recovery handling and clearer logging would enhance agent stability on Windows systems.