Give waycast actual commands #18

New issue

Closed

opened 2026-07-02 04:34:32 +00:00 by javif89 · 0 comments

javif89 commented

2026-07-02 04:34:32 +00:00

Owner

This issue is currently a draft for me to dump my thoughts into:

Right now waycast works a bit too implicitly. First call to waycast starts the daemon, and if the daemon is running, subsequent calls just show the UI.

We already have waycast version.

I would also like to have:

waycast daemon: To be able to start the daemon explicitly on the systemd side
waycast show: This would be the command you set your keybind to. Reduce confusion. Don't want a keybind starting the daemon (see above).
waycast status: To check if the daemon is running or not and diagnose issues
waycast cache clear: In case the cache is getting in the way of new stuff installed and such

Thread is open for any other suggestions/discussion. @xbazzi

This issue is currently a draft for me to dump my thoughts into: Right now waycast works a bit too implicitly. First call to `waycast` starts the daemon, and if the daemon is running, subsequent calls just show the UI. We already have `waycast version`. I would also like to have: - `waycast daemon`: To be able to start the daemon explicitly on the systemd side - `waycast show`: This would be the command you set your keybind to. Reduce confusion. Don't want a keybind starting the daemon (see above). - `waycast status`: To check if the daemon is running or not and diagnose issues - `waycast cache clear`: In case the cache is getting in the way of new stuff installed and such Thread is open for any other suggestions/discussion. @xbazzi

javif89 added the

Code Cleanup

labels

2026-07-02 04:34:32 +00:00

javif89 referenced this issue

2026-07-05 04:24:43 +00:00

refactor: Create application container #38

javif89 self-assigned this

2026-07-06 17:01:49 +00:00

javif89 added this to the (deleted) milestone

2026-07-06 17:48:50 +00:00

javif89 referenced this issue from a pull request that will close it,