aboutsummaryrefslogtreecommitdiffstats
path: root/desktop/modules/ai/README.md
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-10-30 17:34:33 +0100
committerDanilo M. <danix@danix.xyz>2026-10-30 17:34:33 +0100
commit412dec827b5d87c4138491faf49a0babb229f7e2 (patch)
tree3916ccf499c09853e16d2a2c6973fea3a453b877 /desktop/modules/ai/README.md
parent9b9271c304cc7654de0320760f875b666294f591 (diff)
downloadquickshell-412dec827b5d87c4138491faf49a0babb229f7e2.tar.gz
quickshell-412dec827b5d87c4138491faf49a0babb229f7e2.zip
Drop breaktimer and the archived AI apps
breaktimer is parked and imggen and fanfictioner are archived and uninstalled, so the shell was reading files nothing writes and offering buttons that call commands that no longer exist. Status: remove the bt* properties, the file watchers behind them, the verb runner and the presentation-mode pause/resume. The status page loses BreakRow and the tile falls back to "All clear". AI: remove the imggen and fanfictioner rows from ai-state.sh, their labels and controls, and the pid-based fanfictioner stop. The sd-cli engine row stays, since the wallpaper upscaler uses sd-cli too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'desktop/modules/ai/README.md')
-rw-r--r--desktop/modules/ai/README.md10
1 files changed, 4 insertions, 6 deletions
diff --git a/desktop/modules/ai/README.md b/desktop/modules/ai/README.md
index e71159b..d87087a 100644
--- a/desktop/modules/ai/README.md
+++ b/desktop/modules/ai/README.md
@@ -18,10 +18,10 @@ llama's state comes from its API: `/models` for the loaded model, then
`autoload=false` matters: a plain `/slots?model=` on an unloaded model loads
it into VRAM, which is how this was found.
-The sd row covers two processes. A running `sd-cli`, the one-shot runs
-fanfictioner makes, reads up and generating with its model marked `(sd-cli)`,
-whatever the web UI is doing: it holds VRAM for as long as it lives. The first
-version watched only `sd-server` and showed the engine down mid-run.
+The sd row covers two processes. A running one-shot `sd-cli` reads up and
+generating with its model marked `(sd-cli)`, whatever the web UI is doing: it
+holds VRAM for as long as it lives. The first version watched only
+`sd-server` and showed the engine down mid-run.
sd-server has no progress endpoint. Its log, `~/.cache/sd-server.log`, streams
progress bars while it generates, so the row reads busy while the log was
@@ -33,8 +33,6 @@ written in the last 5s. A step slower than that reads idle.
| --- | --- | --- | --- | --- |
| desktop-assistant | `assistant.sh status` | `assistant.sh start` | `assistant.sh stop` | `assistant.sh restart` |
| local chat | `llamachat --ping` | `llamachat --daemon` | `llamachat --quit` | quit, wait for `--ping` to fail (5s at most), `--daemon` |
-| imggen | `imggen status` | `imggen start` (default model) | `imggen stop` | none |
-| fanfictioner | `pgrep` on `python3 .../fanfictioner` | none | TERM its children, then it, by pid | none |
Restart shows only while an app is running. llamachat's `--quit` answers
before the app has exited, so a `--daemon` sent straight after finds it still