cckeep 0.1.1 → 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つは何も変更しません。
 
@@ -43,6 +43,14 @@ npx cckeep            # いま何が見えているか
 npx cckeep doctor     # tmux・ペイン・スケジューラの確認
 ```
 
+**インストール直後に `command not found: cckeep` と出たら**、shim 方式のバージョン管理ツールを使っています。`nodenv` や `asdf` は新しく入った実行ファイルを PATH に出すのに rehash が必要で、`nvm` はシェルを開き直す必要があります。
+
+```sh
+nodenv rehash      # nodenv
+asdf reshim nodejs # asdf
+# nvm: 新しいシェルを開くだけ
+```
+
 条件が一つあります。**Claude Code が tmux の中で動いていること。** 素のターミナルで起動したセッションには別プロセスから入力を送る手段がなく、どんなツールでも手が出せません。→ [tmux で Claude Code を動かす](#tmux-で-claude-code-を動かす)
 
 > 机に戻る手間が省けたなら、⭐ が同じ問題を抱えている人に届く助けになります。
@@ -77,14 +85,16 @@ npx cckeep doctor     # tmux・ペイン・スケジューラの確認
 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 内での起動が必要です。プロセスの再起動は代替になりません — 会話が終わってしまい、守りたかったものそのものを失うからです。
@@ -104,13 +114,31 @@ cc() {
     esac
   done
   local session="claude-$(basename "$PWD")-$(printf '%s' "$PWD" | cksum | cut -d' ' -f1)"
-  if [ -n "$TMUX" ]; then command claude "$@"
-  elif tmux has-session -t "=$session" 2>/dev/null; then tmux attach-session -t "=$session"
-  else tmux new-session -s "$session" -c "$PWD" claude "$@"
+  if [ -n "$TMUX" ]; then command claude "$@"; return; fi
+  if ! tmux has-session -t "=$session" 2>/dev/null; then
+    tmux new-session -s "$session" -c "$PWD" claude "$@"; return
   fi
+
+  # tmux セッションは中の claude より長生きするので、そのままアタッチすると
+  # 会話が消えた素のシェルに落ちることがある。その場合は会話を呼び戻す。
+  local pane_cmd cmd
+  pane_cmd=$(tmux list-panes -t "=$session:" -F '#{pane_current_command}' 2>/dev/null | head -1)
+  case "$pane_cmd" in
+    zsh|bash|sh|fish)
+      cmd="claude"
+      case " $* " in
+        *" -c "*|*" --continue "*|*" -r "*|*" --resume "*|*" --session-id "*) ;;
+        *) cmd="$cmd --continue" ;;
+      esac
+      [ $# -gt 0 ] && cmd="$cmd $*"
+      tmux send-keys -t "=$session:" "$cmd" C-m ;;
+  esac
+  tmux attach-session -t "=$session"
 }
 ```
 
+`cc -c` と `cc --continue` はそのまま使えます — フラグは Claude Code にそのまま渡ります。上のブロックが埋めるのは、フラグでは救えないケース(tmux セッションだけ残って中の Claude Code が終了している状態)です。
+
 あわせて `~/.tmux.conf` に2行必要です。これが無いと tmux 内で Shift+Enter とデスクトップ通知が壊れます([公式の案内](https://code.claude.com/docs/en/terminal-config#configure-tmux))。
 
 ```sh
@@ -136,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:
 
@@ -43,6 +43,16 @@ npx cckeep            # what it sees right now
 npx cckeep doctor     # check tmux, panes, and the scheduler
 ```
 
+**`command not found: cckeep` right after installing?** You are on a shim-based
+version manager. `nodenv` and `rbenv`-style setups need a rehash before a newly
+installed binary appears on `PATH`, and `nvm` needs a new shell:
+
+```sh
+nodenv rehash     # nodenv
+asdf reshim nodejs # asdf
+# nvm: just open a new shell
+```
+
 One requirement: **Claude Code has to be running inside tmux.** A session started in a bare terminal cannot be reached from another process, so there is nothing any tool can do for it. See [Running Claude Code in tmux](#running-claude-code-in-tmux).
 
 > If cckeep saved you a walk back to your desk, a ⭐ helps other Remote Control users find it.
@@ -77,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.
@@ -104,13 +116,33 @@ cc() {
     esac
   done
   local session="claude-$(basename "$PWD")-$(printf '%s' "$PWD" | cksum | cut -d' ' -f1)"
-  if [ -n "$TMUX" ]; then command claude "$@"
-  elif tmux has-session -t "=$session" 2>/dev/null; then tmux attach-session -t "=$session"
-  else tmux new-session -s "$session" -c "$PWD" claude "$@"
+  if [ -n "$TMUX" ]; then command claude "$@"; return; fi
+  if ! tmux has-session -t "=$session" 2>/dev/null; then
+    tmux new-session -s "$session" -c "$PWD" claude "$@"; return
   fi
+
+  # The tmux session outlives the claude process inside it, so attaching can
+  # drop you at a bare shell with the conversation gone. Bring it back.
+  local pane_cmd cmd
+  pane_cmd=$(tmux list-panes -t "=$session:" -F '#{pane_current_command}' 2>/dev/null | head -1)
+  case "$pane_cmd" in
+    zsh|bash|sh|fish)
+      cmd="claude"
+      case " $* " in
+        *" -c "*|*" --continue "*|*" -r "*|*" --resume "*|*" --session-id "*) ;;
+        *) cmd="$cmd --continue" ;;
+      esac
+      [ $# -gt 0 ] && cmd="$cmd $*"
+      tmux send-keys -t "=$session:" "$cmd" C-m ;;
+  esac
+  tmux attach-session -t "=$session"
 }
 ```
 
+`cc -c` and `cc --continue` work as you'd expect — the flag is passed straight
+through to Claude Code. The block above covers the case the flag can't: a tmux
+session whose Claude Code process has already exited.
+
 Claude Code also needs two lines in `~/.tmux.conf`, or Shift+Enter and desktop notifications break inside tmux ([official guidance](https://code.claude.com/docs/en/terminal-config#configure-tmux)):
 
 ```sh
@@ -136,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.1",
+  "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: 'ログはまだありません。',