@hermannbjorgvin/kirby-desktop 1.0.0-beta.5

package/README.md

@@ -0,0 +1,57 @@
+# Kirby Desktop
+
+A desktop app for running AI coding agents across git worktrees, with pull-request review built in.
+
+Kirby gives every branch its own worktree and its own agent session, and puts them in tabs. A pull request opens as a review workspace: the diff with inline comment threads on one side, the agent's terminal on the other. Agents can write draft review comments that you walk through and post. Sessions run under tmux when available, so they survive closing the app.
+
+This is the GUI. The terminal UI ships separately as [`@hermannbjorgvin/kirby`](https://www.npmjs.com/package/@hermannbjorgvin/kirby) and shares the same core — install it too, because it is also how review agents write their comments (see Requirements).
+
+> Beta. Expect rough edges, and pin a version if you depend on it.
+
+## Install
+
+```sh
+npm install -g @hermannbjorgvin/kirby-desktop@beta
+npm install -g @hermannbjorgvin/kirby          # for agent-written reviews
+```
+
+Then, from inside any git repository:
+
+```sh
+kirby-desktop
+```
+
+Launching from a repository opens it directly; launching from anywhere else brings up the repository picker.
+
+## Requirements
+
+- **Node.js 20+** and **git**.
+- **A build toolchain on Linux.** `node-pty` ships prebuilt binaries for macOS and Windows, but not Linux, so npm compiles it during install. On Debian/Ubuntu: `sudo apt install build-essential python3`. macOS needs the Xcode command line tools (`xcode-select --install`); most machines already have them.
+- **An agent CLI** on your `PATH` — `claude`, `codex`, `copilot`, `gemini` or `opencode`. Configurable in Settings.
+- **`kirby` on your `PATH`, for agent-written reviews.** A review agent records its comments by running `kirby util add-comment`, which ships in the [terminal UI package](https://www.npmjs.com/package/@hermannbjorgvin/kirby). Without it the agent reviews the diff and has nowhere to put what it found. Everything else here works without it.
+- **`tmux` (optional, recommended).** With it, agent sessions keep running when you quit and are reattached next launch.
+- **`gh` or `az` (optional)** for pull-request features, on GitHub and Azure DevOps respectively.
+
+Installing pulls Electron's binary (~100–200 MB) on first install.
+
+### Windows
+
+Run it under WSL 2, which gives you the unix environment the agent and tmux backends expect. WSLg renders the app as a normal Windows window. Keep your repositories on the Linux filesystem (`~/code/...`) rather than `/mnt/c/...` — git across the filesystem boundary is dramatically slower.
+
+## What it does
+
+- **Worktree per branch.** Check out any branch as a worktree from the command palette; remove it (branch and session included) when you're done. Merged branches are cleaned up automatically, unless an agent is still working in one.
+- **Agent sessions in tabs.** Launch an agent on a branch, watch it work, and keep its scrollback when you switch tabs. Tabs show when an agent is busy and flag it when it finishes something you haven't looked at.
+- **Pull request review.** Whole-file diffs with folding, split and unified views, and word-level highlighting. Comment threads render inline, including images behind provider auth. Reply, resolve and submit your verdict without leaving the app.
+- **Agent-written reviews.** Launch an agent to review a PR and it writes draft comments anchored to lines, through `kirby util add-comment` (see Requirements). Step through them by severity, edit or discard, and post.
+
+## Configuration
+
+Settings live in the app (⌘, / Ctrl+,) and are stored in `~/.kirby/`. Provider credentials, the agent command, keybinding preset (Normie or Vim), terminal backend and poll intervals are all configurable there.
+
+## Links
+
+- [Source](https://github.com/HermannBjorgvin/kirby)
+- [Issues](https://github.com/HermannBjorgvin/kirby/issues)
+
+MIT

package/launcher.mjs

@@ -0,0 +1,42 @@
+#!/usr/bin/env node
+// Global-install entry point for kirby-desktop (`bin` in the dist
+// package.json). Spawns the Electron binary against this app
+// directory. Mirrors dev.mjs's SUID-sandbox fallback: npm-installed
+// Electron often can't use its setuid helper, and crashing with
+// SIGTRAP is a terrible first-run experience.
+import { spawn } from 'node:child_process';
+import { statSync } from 'node:fs';
+import { createRequire } from 'node:module';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const require = createRequire(import.meta.url);
+const appDir = dirname(fileURLToPath(import.meta.url));
+const electron = require('electron'); // string: path to the electron binary
+const { version } = require(join(appDir, 'package.json'));
+
+const args = [];
+try {
+  const st = statSync(
+    join(appDir, 'node_modules', 'electron', 'dist', 'chrome-sandbox')
+  );
+  if (!(st.uid === 0 && (st.mode & 0o4755) === 0o4755)) {
+    console.warn(
+      '[kirby-desktop] SUID sandbox unavailable — launching with --no-sandbox'
+    );
+    args.push('--no-sandbox');
+  }
+} catch {
+  args.push('--no-sandbox');
+}
+
+const child = spawn(electron, [...args, appDir], {
+  stdio: 'inherit',
+  // Launching from inside a repo auto-opens that repo.
+  env: {
+    ...process.env,
+    KIRBY_START_DIR: process.cwd(),
+    KIRBY_DESKTOP_VERSION: version,
+  },
+});
+child.on('close', (code) => process.exit(code ?? 0));