cckeep 0.1.2 → 0.2.0

package/README.ja.md

@@ -29,12 +29,12 @@
 
 ```sh
 npm install -g cckeep
-cckeep install
+cckeep enable
 ```
 
-バックグラウンドジョブを登録します(macOS は launchd、Linux は systemd user timer)。15秒ごとに確認し、死んでいるものを繋ぎ直します。
+`npm install` は CLI を `PATH` に置くだけで、常駐はまだ始まりません。`cckeep enable` がバックグラウンドジョブを登録します(macOS は launchd、Linux は systemd user timer)。15秒ごとに確認し、死んでいるものを繋ぎ直します。
 
-`npx cckeep install` ではなくグローバルに入れてください。登録されたジョブはインストール先の cckeep を実行しますが、npx のキャッシュは使い捨てです。そこを指すジョブはキャッシュが消された瞬間に、黙って動かなくなります — 監視ツールが持ってはいけない唯一の壊れ方です。そのため `cckeep install` は npx のパスからの登録を拒否します。
+`npx cckeep enable` ではなくグローバルに入れてください。登録されたジョブはインストール先の cckeep を実行しますが、npx のキャッシュは使い捨てです。そこを指すジョブはキャッシュが消された瞬間に、黙って動かなくなります — 監視ツールが持ってはいけない唯一の壊れ方です。そのため `cckeep enable` は npx のパスからの登録を拒否します。
 
 入れる前に様子を見るだけなら `npx` で構いません。以下の2つは何も変更しません。
 
@@ -85,14 +85,16 @@ asdf reshim nodejs # asdf
 cckeep                 # 状態表示: Claude Code のペインごとに1行
 cckeep watch           # スケジュール登録せずフォアグラウンドで実行
 cckeep once            # 1回だけ実行(スケジューラが叩くもの)
-cckeep install         # バックグラウンドジョブを登録
-cckeep uninstall       # 解除
+cckeep enable          # バックグラウンドでの監視を開始
+cckeep disable         # 監視を停止
 cckeep doctor          # tmux・ペイン・スケジューラ・各パス
 cckeep logs            # これまでの動作
 ```
 
 オプション: `--dry-run`、`--json`、`--interval <秒>`、`--lang en|ja`(`LANG` から自動判定)。
 
+`install` / `uninstall` は `enable` / `disable` のエイリアスとして引き続き使えます。
+
 ## tmux で Claude Code を動かす
 
 cckeep は tmux ペインを読み、そこに入力します。動いている Claude Code セッションに別プロセスから届く経路はこれだけで、だからこそ tmux 内での起動が必要です。プロセスの再起動は代替になりません — 会話が終わってしまい、守りたかったものそのものを失うからです。
@@ -162,7 +164,7 @@ Ctrl+B の衝突は対処不要です。Claude Code は tmux を検出して、
 }
 ```
 
-- `interval` — 巡回間隔(秒)。`install` が登録する間隔でもある
+- `interval` — 巡回間隔(秒)。`enable` が登録する間隔でもある
 - `cooldown` — 同じペインに再度手を出せるまでの秒数
 - `stuckLimit` — `reconnecting` が何回続いたら固着とみなすか
 - `missLimit` — 表示のあったペインが何回無表示なら繋ぎ直すか

package/README.md

@@ -29,12 +29,12 @@ Either way you find out the same way: you reach for your phone, and the session
 
 ```sh
 npm install -g cckeep
-cckeep install
+cckeep enable
 ```
 
-That registers a background job — launchd on macOS, a systemd user timer on Linux — that checks every 15 seconds and re-arms whatever went dead.
+`npm install` only puts the CLI on your `PATH`; `cckeep enable` is the step that registers a background job — launchd on macOS, a systemd user timer on Linux — that checks every 15 seconds and re-arms whatever went dead.
 
-Install it globally rather than running `npx cckeep install`. The scheduled job runs cckeep from wherever it was installed, and npx's cache is throwaway: a job pointing into it keeps working until the cache is cleared and then stops, silently — the one failure a watchdog must not have. `cckeep install` refuses to schedule from an npx path for that reason.
+Install it globally rather than running `npx cckeep enable`. The scheduled job runs cckeep from wherever it was installed, and npx's cache is throwaway: a job pointing into it keeps working until the cache is cleared and then stops, silently — the one failure a watchdog must not have. `cckeep enable` refuses to schedule from an npx path for that reason.
 
 To look before installing anything, `npx` is fine — neither of these changes a thing:
 
@@ -87,14 +87,16 @@ This is the whole design problem. A watchdog that types into your terminal on a
 cckeep                 # status: one line per Claude Code pane
 cckeep watch           # run in the foreground instead of scheduling
 cckeep once            # a single pass — what the scheduler runs
-cckeep install         # register the background job
-cckeep uninstall       # remove it
+cckeep enable          # start checking in the background
+cckeep disable         # stop checking
 cckeep doctor          # tmux, panes, scheduler, paths
 cckeep logs            # what it has done
 ```
 
 Options: `--dry-run`, `--json`, `--interval <s>`, `--lang en|ja` (auto-detected from `LANG`).
 
+`install` and `uninstall` still work as aliases for `enable` and `disable`.
+
 ## Running Claude Code in tmux
 
 cckeep reads and types into tmux panes. That is the only channel a separate process has into a live Claude Code session — and it is why the session must be started inside tmux. Restarting the process is not an alternative: it would end the conversation, which is exactly what you are trying to save.
@@ -166,7 +168,7 @@ Defaults are tuned so you never notice it. Override in `~/.cckeep/config.json`,
 }
 ```
 
-- `interval` — seconds between passes (also what `install` schedules)
+- `interval` — seconds between passes (also what `enable` schedules)
 - `cooldown` — seconds before the same pane may be acted on again
 - `stuckLimit` — checks in `reconnecting` before the bridge is treated as wedged
 - `missLimit` — checks with no indicator before re-arming a pane that had one

package/bin/cckeep.js

@@ -7,6 +7,7 @@ import { logPath, statePath, homeDir } from '../src/state.js';
 import * as tmux from '../src/tmux.js';
 import * as scheduler from '../src/scheduler.js';
 import { pickLang, strings } from '../src/i18n.js';
+import { resolveCommand } from '../src/commands.js';
 
 const HELP = `cckeep — keep Claude Code Remote Control from silently going dead
 
@@ -17,11 +18,14 @@ COMMANDS
   status          what cckeep sees right now (default)
   watch           run in the foreground, one pass every --interval seconds
   once            a single pass — what the scheduler runs
-  install         register a background job (launchd on macOS, systemd on Linux)
-  uninstall       remove it
+  enable          start checking in the background (launchd / systemd user timer)
+  disable         stop checking
   doctor          check tmux, Claude Code panes, and the scheduler
   logs            show recent actions
 
+  "npm install -g cckeep" only puts this CLI on your PATH. "cckeep enable" is
+  what registers the background job. (install / uninstall still work as aliases.)
+
 OPTIONS
   --interval <s>  seconds between passes (default 15)
   --dry-run       report what would be sent, send nothing
@@ -107,7 +111,7 @@ async function main() {
     process.exit(1);
   }
 
-  switch (opts.command ?? 'status') {
+  switch (resolveCommand(opts.command)) {
     case 'status': {
       const out = await runPass({ config, dryRun: true });
       render(out, t, opts);
@@ -128,7 +132,7 @@ async function main() {
         await new Promise((r) => setTimeout(r, config.interval * 1000));
       }
     }
-    case 'install': {
+    case 'enable': {
       const res = scheduler.install({ interval: config.interval });
       if (res.kind === 'ephemeral') {
         console.error(t.ephemeral(res.path));
@@ -138,14 +142,14 @@ async function main() {
         console.log(t.unsupported);
         process.exit(1);
       }
-      console.log(res.ok ? t.installed(res.kind, res.path) : t.installFailed(res.kind));
+      console.log(res.ok ? t.enabled(res.kind, res.path) : t.enableFailed(res.kind));
       if (!res.ok) process.exit(1);
       break;
     }
-    case 'uninstall': {
+    case 'disable': {
       const res = scheduler.uninstall();
       if (res.kind === 'unsupported') return console.log(t.unsupported);
-      console.log(t.uninstalled(res.kind));
+      console.log(t.disabled(res.kind));
       break;
     }
     case 'doctor': {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cckeep",
-  "version": "0.1.2",
+  "version": "0.2.0",
   "description": "Keeps Claude Code Remote Control from silently going dead. Re-arms the sessions its 31-second retry budget gives up on — local, tmux-native, zero dependencies.",
   "type": "module",
   "bin": {

package/src/commands.js

@@ -0,0 +1,35 @@
+/**
+ * `npm install -g cckeep` puts the CLI on your PATH; registering the background
+ * job is a separate, deliberate step. Naming that step `install` too made the
+ * quick start read as if you were installing twice, so the scheduler verbs are
+ * `enable` / `disable` — the same words systemctl uses for the same idea.
+ *
+ * The old names stay as aliases: they shipped in 0.1.x and in the plists people
+ * already generated, and breaking them buys nothing.
+ */
+export const ALIASES = {
+  install: 'enable',
+  uninstall: 'disable',
+};
+
+export const COMMANDS = new Set([
+  'status',
+  'watch',
+  'once',
+  'enable',
+  'disable',
+  'doctor',
+  'logs',
+  'help',
+  'version',
+]);
+
+/** Map whatever the user typed onto a canonical command. */
+export function resolveCommand(input) {
+  const name = input ?? 'status';
+  return ALIASES[name] ?? name;
+}
+
+export function isKnownCommand(input) {
+  return COMMANDS.has(resolveCommand(input));
+}

package/src/config.js

@@ -5,7 +5,7 @@ import { DEFAULTS } from './detect.js';
 
 export const BASE = {
   ...DEFAULTS,
-  /** Seconds between passes in watch mode, and what `install` schedules. */
+  /** Seconds between passes in watch mode, and what `enable` schedules. */
   interval: 15,
   /** Milliseconds between the two captures of the idle check. */
   settle: 2000,

package/src/i18n.js

@@ -17,11 +17,11 @@ const en = {
   wouldRearm: 'would re-arm',
   wouldConfirm: 'would cycle bridge',
   watching: (n) => `Watching every ${n}s. Ctrl+C to stop.`,
-  installed: (kind, path) => `Installed (${kind}): ${path}`,
-  installFailed: (kind) => `Wrote the ${kind} unit, but could not load it. Load it manually, or run \`cckeep watch\` in a terminal.`,
-  uninstalled: (kind) => `Removed the ${kind} job.`,
+  enabled: (kind, path) => `Enabled (${kind}): ${path}`,
+  enableFailed: (kind) => `Wrote the ${kind} unit, but could not load it. Load it manually, or run \`cckeep watch\` in a terminal.`,
+  disabled: (kind) => `Disabled — removed the ${kind} job.`,
   unsupported: 'Automatic scheduling supports macOS (launchd) and Linux (systemd user timers). Elsewhere, run `cckeep watch` under your own supervisor.',
-  ephemeral: (p) => `Refusing to schedule: this copy of cckeep lives in npm's throwaway npx cache\n  ${p}\nA scheduled job pointing there stops working the moment the cache is cleared — silently. Install it properly first:\n\n  npm install -g cckeep && cckeep install\n`,
+  ephemeral: (p) => `Refusing to schedule: this copy of cckeep lives in npm's throwaway npx cache\n  ${p}\nA scheduled job pointing there stops working the moment the cache is cleared — silently. Install it properly first:\n\n  npm install -g cckeep && cckeep enable\n`,
   scheduledPath: 'scheduled cmd',
   scheduledMissing: 'MISSING — run `cckeep install` again',
   noLog: 'No log yet.',
@@ -48,11 +48,11 @@ const ja = {
   wouldRearm: '再接続を送信する',
   wouldConfirm: 'ブリッジを張り直す',
   watching: (n) => `${n} 秒ごとに監視します。Ctrl+C で停止。`,
-  installed: (kind, path) => `登録しました (${kind}): ${path}`,
-  installFailed: (kind) => `${kind} の定義は書きましたが、読み込みに失敗しました。手動で読み込むか、ターミナルで \`cckeep watch\` を実行してください。`,
-  uninstalled: (kind) => `${kind} のジョブを削除しました。`,
+  enabled: (kind, path) => `有効化しました (${kind}): ${path}`,
+  enableFailed: (kind) => `${kind} の定義は書きましたが、読み込みに失敗しました。手動で読み込むか、ターミナルで \`cckeep watch\` を実行してください。`,
+  disabled: (kind) => `無効化しました — ${kind} のジョブを削除しました。`,
   unsupported: '自動スケジュール登録は macOS (launchd) と Linux (systemd user timer) に対応しています。それ以外では `cckeep watch` を任意の常駐手段で動かしてください。',
-  ephemeral: (p) => `登録を中止しました: この cckeep は npm の使い捨て npx キャッシュ内にあります\n  ${p}\nここを指すジョブは、キャッシュが消された瞬間に黙って動かなくなります。先に正式にインストールしてください:\n\n  npm install -g cckeep && cckeep install\n`,
+  ephemeral: (p) => `登録を中止しました: この cckeep は npm の使い捨て npx キャッシュ内にあります\n  ${p}\nここを指すジョブは、キャッシュが消された瞬間に黙って動かなくなります。先に正式にインストールしてください:\n\n  npm install -g cckeep && cckeep enable\n`,
   scheduledPath: '登録先',
   scheduledMissing: '見つかりません — `cckeep install` を再実行してください',
   noLog: 'ログはまだありません。',