larkway 0.3.58 → 0.3.60

package/README.md

@@ -8,7 +8,7 @@
 
 You @ the bot in a Feishu thread. It runs on your machine — reading your real codebase, executing commands, opening MRs — and posts the result back. You define what the agent knows and what it can do. Larkway just carries the messages.
 
-**Current release: v0.3.58**
+**Current release: v0.3.60**
 
 ---
 
@@ -61,7 +61,7 @@ Feishu thread
 
 **What Larkway does NOT do** — the agent decides everything else:
 
-- No GitLab/GitHub API calls (the agent runs `glab`/`gh` itself)
+- No GitHub/GitLab API calls (the agent runs `gh`/`glab` itself)
 - No worktree creation (the agent runs `git worktree add`)
 - No dev server management (the agent starts it)
 - No orchestration logic — the agent reads your `AGENTS.md` / `CLAUDE.md` / skills and plans its own steps
@@ -163,6 +163,7 @@ Secrets live only in `~/.larkway/.env` (mode 0600). Config and memory contain no
 - **Session continuity** — every Feishu thread maps to a persistent `session_id`; the agent remembers what it did in prior turns
 - **Agent Workspace** — each bot gets its own workspace where the agent clones the repo itself, with per-thread session dirs; concurrent threads don't trip over each other's git state (expect disk usage and a slower first turn on large repos — clones are per-session, GC'd after 24h idle)
 - **Codex runtime pre-checks** — `larkway doctor` validates Codex state directory writability before start
+- **OS-service daemon** — `larkway start` registers the bridge with launchd (macOS) / systemd (Linux): survives reboots and auto-restarts on crash; `larkway stop` stops it and disables autostart
 - **Topic ↔ Feishu task handle** — turn a topic into a Feishu task and the agent claims it, then keeps its lifecycle (done/failed/reopened, stalled, handed off, overdue) in sync automatically — see below
 
 ---
@@ -194,10 +195,11 @@ platform-fact writeups: [docs/task-handle.md](docs/task-handle.md).
 
 ## Requirements
 
+- **macOS or Linux** — native Windows is not supported yet (the runtime depends on POSIX tooling such as `bash` and `pgrep`); on Windows, install and run everything (Node.js, larkway, Claude Code / Codex, `lark-cli`) inside [WSL](https://learn.microsoft.com/windows/wsl/install)
 - **Node.js 20+ LTS**
 - **A Claude Code or Codex subscription** with local CLI installed and logged in
 - **`lark-cli`** — Feishu long-connection client and message utilities: `npm i -g @larksuite/cli`, then `lark-cli auth login` (the agent uses it to read thread history and attachments; `larkway doctor` checks it's present)
-- **`glab` + `git`** — for bots that open MRs (optional for read-only bots)
+- **`git` + `gh`** — for bots that open PRs (GitHub is the default forge; use `glab` instead for GitLab repos; both optional for read-only bots)
 - **An always-on host machine** — the bridge must stay running to receive Feishu events; a laptop that sleeps will miss messages; a small server or desktop works well
 
 ---

package/README.zh.md

@@ -8,7 +8,7 @@
 
 你在飞书话题里 @ bot，它在你的机器上运行——读真实代码库、执行命令、开 MR——把结果贴回飞书。你定义 agent 知道什么、能做什么。Larkway 只负责传递消息。
 
-**当前版本：v0.3.58**
+**当前版本：v0.3.60**
 
 ---
 

package/bin/larkway.mjs

@@ -0,0 +1,51 @@
+#!/usr/bin/env node
+// larkway CLI shim — resolves the package root from this script's own location
+// so it works whether invoked via `bin/larkway`, an absolute path, or a symlink
+// on PATH (e.g. after `npm i -g`).
+//
+// Written in Node (not bash) so npm's cross-platform bin shims work everywhere:
+// a bash shebang made Windows installs fail at startup with
+// `/bin/bash: C:Users...: No such file or directory` before any of our code ran.
+//
+// Startup priority:
+//   1. dist/cli/index.js exists  → import it in-process (installed package / post-build)
+//   2. otherwise                 → `npx tsx src/cli/index.ts` (fresh clone dev mode, no build)
+import { existsSync } from "node:fs";
+import { spawnSync } from "node:child_process";
+import path from "node:path";
+import { fileURLToPath, pathToFileURL } from "node:url";
+
+if (process.platform === "win32") {
+  // The bridge runtime depends on POSIX tooling (bash supervisor, pgrep, lsof),
+  // so native Windows is not supported yet — fail fast with guidance instead of
+  // crashing later with an obscure error.
+  console.error(
+    [
+      "larkway 暂不支持原生 Windows 运行(依赖 bash / pgrep 等 POSIX 工具)。",
+      "推荐在 WSL(Windows Subsystem for Linux)中安装使用:",
+      "  1. 安装 WSL: https://learn.microsoft.com/windows/wsl/install",
+      "  2. 在 WSL 终端内安装 Node.js 20+,然后 `npm i -g larkway`",
+      "  3. Claude Code / Codex 也需安装在 WSL 内",
+      "",
+      "larkway does not yet support native Windows (it depends on POSIX tooling",
+      "such as bash and pgrep). Please install and run it inside WSL instead.",
+    ].join("\n"),
+  );
+  process.exit(1);
+}
+
+const selfPath = fileURLToPath(import.meta.url);
+const repoRoot = path.resolve(path.dirname(selfPath), "..");
+const distEntry = path.join(repoRoot, "dist", "cli", "index.js");
+
+if (existsSync(distEntry)) {
+  await import(pathToFileURL(distEntry).href);
+} else {
+  // Dev fallback: run TypeScript source directly via tsx.
+  const result = spawnSync(
+    "npx",
+    ["tsx", path.join(repoRoot, "src", "cli", "index.ts"), ...process.argv.slice(2)],
+    { stdio: "inherit" },
+  );
+  process.exit(result.status ?? 1);
+}