Better observability and user feedback #14

Open
opened 2026-07-02 03:45:30 +00:00 by javif89 · 1 comment
Owner

Currently, if the daemon gets stuck in a crash loop, the user has no way to know other than the fact that waycast just isn't working properly. We should make sure to have good error logging plus a waycast status command that will check if the daemon is healthy or not.

Currently, if the daemon gets stuck in a crash loop, the user has no way to know other than the fact that waycast just isn't working properly. We should make sure to have good error logging plus a `waycast status` command that will check if the daemon is healthy or not.
javif89 added this to the v1.1.0 milestone 2026-07-02 03:46:12 +00:00
Author
Owner

The waycast status command was added in #45. Better error logging could still happen such as:

  • Sending a notification on crash
The waycast status command was added in #45. Better error logging could still happen such as: - Sending a notification on crash
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
waycasthq/waycast#14
No description provided.