larkway 0.3.59 → 0.3.61

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.59**
+**Current release: v0.3.61**
 
 ---
 
@@ -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
 
 ---

package/README.zh.md

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

package/bin/larkway.mjs

@@ -16,22 +16,31 @@ 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);
+  // Native Windows support is implemented (cross-spawn layer + schtasks
+  // service adapter) but not yet validated on real hardware, so it stays
+  // behind an explicit opt-in until then. Default: fail fast with WSL
+  // guidance instead of letting users hit rough edges unwarned.
+  if (process.env.LARKWAY_EXPERIMENTAL_WINDOWS === "1") {
+    console.error(
+      "[larkway] native Windows support is EXPERIMENTAL (LARKWAY_EXPERIMENTAL_WINDOWS=1) — please report issues.",
+    );
+  } else {
+    console.error(
+      [
+        "larkway 的原生 Windows 支持仍在验证中,默认未开放。",
+        "推荐在 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 内",
+        "",
+        "想帮忙试用原生 Windows(实验性):设置环境变量 LARKWAY_EXPERIMENTAL_WINDOWS=1 后重试,并欢迎反馈问题。",
+        "",
+        "Native Windows support is implemented but still being validated.",
+        "Use WSL for now, or set LARKWAY_EXPERIMENTAL_WINDOWS=1 to try the experimental native mode.",
+      ].join("\n"),
+    );
+    process.exit(1);
+  }
 }
 
 const selfPath = fileURLToPath(import.meta.url);