From 8e95332552291f316ffc20862268af6ad5128bb5 Mon Sep 17 00:00:00 2001 From: marcus hinz Date: Wed, 22 Jul 2026 12:35:54 +0200 Subject: [PATCH] =?UTF-8?q?README:=20Windows=20und=20AppImage=20gestrichen?= =?UTF-8?q?=20=E2=80=94=20beides=20wird=20nicht=20ausgeliefert?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- README.md | 17 ++++------------- 1 file changed, 4 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index f4fa889..e1f021f 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ **Get Claude Code organized** -Pool, project, and session management for [Claude Code](https://claude.com/claude-code) — a tray app with a built-in terminal, a draft panel, and a per-project document archive. macOS and Linux; Windows support follows. (Repository and binary name: `ai-control`.) +Pool, project, and session management for [Claude Code](https://claude.com/claude-code) — a tray app with a built-in terminal, a draft panel, and a per-project document archive. macOS and Linux. (Repository and binary name: `ai-control`.) > All code in this project was generated by Claude (Claude Code). @@ -83,10 +83,7 @@ Or avoid the topic entirely and build from source (below) — self-built apps ar ### Linux -Releases carry a `.deb`, an `.rpm`, and an AppImage. - -- **deb / rpm** — recommended. Both install three desktop-integration pieces alongside the app: the **GNOME Shell extension** `ai-control-popup@local` (tray button + popup on GNOME, `/usr/share/gnome-shell/extensions/`), the **Cinnamon extension** `ai-control-popup@local` (popup placement on Wayland, initial focus on X11, `/usr/share/cinnamon/extensions/`), and the **KWin script** `ai-control-popup` (popup placement on KDE Wayland, `/usr/share/kwin/scripts/`). -- **AppImage** — runs on desktops with a standard tray (KDE, XFCE, Cinnamon). On GNOME it refuses to start and points to the deb/rpm: the tray there needs the shell extension, which an installation-free AppImage cannot provide. +Releases carry a `.deb` and an `.rpm`. Both install three desktop-integration pieces alongside the app: the **GNOME Shell extension** `ai-control-popup@local` (tray button + popup on GNOME, `/usr/share/gnome-shell/extensions/`), the **Cinnamon extension** `ai-control-popup@local` (popup placement on Wayland, initial focus on X11, `/usr/share/cinnamon/extensions/`), and the **KWin script** `ai-control-popup` (popup placement on KDE Wayland, `/usr/share/kwin/scripts/`). Tray integration by desktop: GNOME via the bundled shell extension, KDE Wayland via StatusNotifierItem plus the bundled KWin script for popup placement, KDE X11/XFCE/Cinnamon via StatusNotifierItem directly. On Cinnamon the bundled extension additionally places the popup at the tray icon on **Wayland** (a Wayland client cannot position its own window) and gives it initial focus on **X11** (Muffin's focus-stealing prevention would otherwise drop it). @@ -100,10 +97,6 @@ The app **enables the matching piece automatically** on each start, per user and The installers are hand-tested per release. Current state: Fedora 44 via rpm on GNOME, KDE Plasma, Cinnamon, and XFCE (VM test fleet); Ubuntu 26.04 (GNOME), Kubuntu (KDE Plasma, Wayland) and Linux Mint (Cinnamon) via deb in earlier rounds. The two open findings from that round are resolved: popup placement on Cinnamon Wayland now comes from the bundled Cinnamon extension, and click-outside-to-close verified fine on XFCE and Cinnamon. macOS re-test of the current build is in progress. -### Windows - -Follows. - ## Architecture One binary, three process roles: @@ -168,8 +161,7 @@ Deleting a project is scoped in three stages, each preceded by a preview of the ├── dev.sh development mode (tauri dev) ├── build.sh release build for the current OS (see below) ├── deploy-linux.sh install the freshest local bundle (rpm/deb) -├── deploy-macos.sh install the fresh .app into ~/Applications -└── deploy-windows.ps1 run the freshest NSIS installer +└── deploy-macos.sh install the fresh .app into ~/Applications ``` The three process roles that binary takes are described under [Architecture](#architecture). @@ -193,11 +185,10 @@ The three process roles that binary takes are described under [Architecture](#ar ./deploy-macos.sh # …then install it (pick the script for your OS) ``` -`build.sh` picks the bundles by platform: macOS `.app` + DMG, Linux deb + rpm, Windows NSIS. Installing is the job of the matching deploy script: +`build.sh` picks the bundles by platform: macOS `.app` + DMG, Linux deb + rpm. Installing is the job of the matching deploy script: - **`deploy-macos.sh`** — installs the fresh bundle into `~/Applications` (replacing the previous copy) and registers it with Launch Services. The build output is then moved into `bundle/macos.noindex/` and unregistered, so Spotlight and the launcher only ever find the installed copy. It refuses to run while `ai-control` is still running. - **`deploy-linux.sh`** — installs the freshest local bundle via `rpm`/`dpkg`. -- **`deploy-windows.ps1`** — runs the freshest NSIS installer. Build dependencies on Linux: `webkit2gtk-4.1`, `libgtk-3`, `libayatana-appindicator3`, `librsvg2`, `patchelf`.