Problem
Currently, users have no clear indication of whether the bot is actively running or reachable. In scenarios where the host machine is locked, offline, or the OpenCode server is not running, the bot becomes unresponsive without any visible status change.
This lack of feedback can lead to confusion, as users cannot easily determine whether the issue is with the bot’s availability or message processing delays.
Proposal
Introduce a configurable presence indicator by appending an Online/Offline status to the bot’s display name. For example:
Bot_Name (Online) -- when the bot is active and reachable
Bot_Name (Offline) -- when the bot is inactive or unreachable
This status could be dynamically updated based on the bot’s connectivity or server health. The feature should be optional and controlled via configuration, allowing users to enable or disable it as needed.
Additionally, the implementation could leverage existing mechanisms (e.g., setMyName or equivalent APIs) to update the bot’s display name dynamically.
Potential Enhancements:
Detect and handle messages sent while the bot is offline, enabling deferred processing once the bot comes back online. Provide more granular states in the future (e.g., Starting, Idle, Error). Integrate health checks or heartbeat signals for accurate status updates
Benefits:
Improves user experience by providing immediate visibility into bot availability. Reduces confusion around unresponsive behavior. Enables better debugging and operational awareness
Done criteria (optional)
No response
Problem
Currently, users have no clear indication of whether the bot is actively running or reachable. In scenarios where the host machine is locked, offline, or the OpenCode server is not running, the bot becomes unresponsive without any visible status change.
This lack of feedback can lead to confusion, as users cannot easily determine whether the issue is with the bot’s availability or message processing delays.
Proposal
Introduce a configurable presence indicator by appending an Online/Offline status to the bot’s display name. For example:
Bot_Name (Online) -- when the bot is active and reachable
Bot_Name (Offline) -- when the bot is inactive or unreachable
This status could be dynamically updated based on the bot’s connectivity or server health. The feature should be optional and controlled via configuration, allowing users to enable or disable it as needed.
Additionally, the implementation could leverage existing mechanisms (e.g., setMyName or equivalent APIs) to update the bot’s display name dynamically.
Potential Enhancements:
Detect and handle messages sent while the bot is offline, enabling deferred processing once the bot comes back online. Provide more granular states in the future (e.g., Starting, Idle, Error). Integrate health checks or heartbeat signals for accurate status updates
Benefits:
Improves user experience by providing immediate visibility into bot availability. Reduces confusion around unresponsive behavior. Enables better debugging and operational awareness
Done criteria (optional)
No response