cckeep 0.2.3 → 0.2.4

package/README.ja.md

@@ -72,7 +72,7 @@ asdf reshim nodejs # asdf
 
 | 画面の状態 | 意味 | cckeep の動作 |
 |---|---|---|
-| `/rc active` | 接続できている | ペインを覚えるだけ |
+| `/rc active`、または切り詰められた `/rc` | 接続できている | ペインを覚えるだけ |
 | `/rc reconnecting` | 31秒の再試行中 | 待つ(たいていはこれで戻る) |
 | `/rc reconnecting` が2分以上 | 固まっている([#34255](https://github.com/anthropics/claude-code/issues/34255)) | パネルを開いて切断し、繋ぎ直す |
 | `Remote Control disconnected` | 諦めた | すぐに繋ぎ直す |
@@ -199,6 +199,8 @@ Claude Code はフッターにリモートコントロールの状態を表示
 
 ペインを探すところに一手間あります。Claude Code は自身のプロセスタイトルを書き換えるため、tmux はそのペインのコマンド名を `claude` ではなく `2.1.220` のように報告します。tmux の報告する名前だけで判定すると、実機では1つも見つかりません。そこで cckeep はプロセステーブルも参照し、ペインのプロセス(またはそこから起動されたプロセス)が実際に `claude` であればそのペインを対象とします。
 
+インジケータは右寄せで描画されるため、カスタムステータスラインを使っていたりペインが狭かったりすると、`active` が削られて `/rc` だけになります。cckeep はこれを接続中として扱います。インジケータ自体は接続がある間しか描画されず、接続中と読んでもペインを記録して待つだけなので、안全な側に倒れるからです。
+
 「どこを見るか」も同じくらい重要です。状態の判定に使う文字列は画面末尾の十数行からしか読みません。これらの言葉は普通の会話にも出てくるので、たとえば `/rc active` について話しているだけのセッションが「接続中」に見えてしまうからです。逆にダイアログとステータスパネルの検出は画面全体を対象にしています。こちらは誤検知しても1回見送るだけで済みますが、見落とすと誤ったキー入力に直結します。
 
 判定層(`src/detect.js`)は、画面テキストと直前の状態だけを受け取る純粋関数です。だからこそ、安全ルールをターミナル無しで網羅的にテストできます。静止判定・直前の再確認・キー送信といった I/O は、実行層(`src/run.js`)が担当します。

package/README.md

@@ -74,7 +74,7 @@ This is the whole design problem. A watchdog that types into your terminal on a
 
 | State on screen | What it means | What cckeep does |
 |---|---|---|
-| `/rc active` | connected | remembers the pane, nothing else |
+| `/rc active`, or a truncated `/rc` | connected | remembers the pane, nothing else |
 | `/rc reconnecting` | inside the 31-second budget | waits — this usually resolves |
 | `/rc reconnecting`, 2 minutes on | wedged ([#34255](https://github.com/anthropics/claude-code/issues/34255)) | cycles the bridge: opens the panel, disconnects, reconnects |
 | `Remote Control disconnected` | gave up | re-arms immediately |
@@ -203,6 +203,8 @@ Claude Code paints a Remote Control indicator in its footer: `/rc active` when c
 
 Finding those panes takes one extra step: Claude Code rewrites its own process title, so tmux reports such a pane as `2.1.220` rather than `claude`. Matching the name tmux reports therefore finds nothing on a real machine. cckeep checks the process table as well, and treats a pane as Claude Code's when the pane's process — or anything it spawned — is actually `claude`.
 
+The indicator is right-aligned, so a custom status line or a narrow pane squeezes it down to a bare `/rc` with the word cut off. cckeep treats that as connected: the indicator only renders while a link exists, and reading it as connected merely records the pane and waits.
+
 Where it looks matters as much as what it looks for. The state indicators are read from the last dozen lines only, because the words themselves turn up in ordinary conversation — a session where you happen to discuss `/rc active` would otherwise read as connected. Dialog and status-panel detection deliberately scans the whole pane instead: a false positive there costs one skipped pass, while a miss costs a keystroke in the wrong place.
 
 The decision layer (`src/detect.js`) is a pure function of screen text plus prior state, which is why the safety rules can be tested exhaustively without a terminal. The runner (`src/run.js`) does the I/O: the idle check, the last-moment re-check, and the keystrokes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cckeep",
-  "version": "0.2.3",
+  "version": "0.2.4",
   "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/detect.js

@@ -3,10 +3,25 @@
 // so every rule below is directly testable, which matters a lot for a tool whose
 // failure mode is typing into someone's terminal at the wrong moment.
 
-/** Indicators Claude Code paints in the footer for the Remote Control link. */
-const CONNECTED = '/rc active';
-const RETRYING = '/rc reconnecting';
-const FAILED = /Remote Control disconnected|Remote Control failed|\/rc failed/;
+/**
+ * The Remote Control indicator Claude Code right-aligns in its footer.
+ *
+ * It reads `/rc active`, `/rc reconnecting` or `/rc failed` when there is room
+ * — but it is right-aligned on the status line, so a custom statusline or a
+ * narrow pane truncates it to a bare `/rc`. Matching the full phrase therefore
+ * never fires for anyone with a status line of their own, which is common.
+ *
+ * Anchored to the end of the line because the indicator is right-aligned. A
+ * separator and link may follow it (`/rc active · claude.ai/code`), but prose
+ * may not — that is what keeps `/rc` written mid-sentence from matching.
+ */
+const RC_INDICATOR = /(?:^|\s)\/rc(?:\s+(active|reconnecting|failed))?(?:\s*[\u00b7|].*)?\s*$/;
+
+/** Lines a user types into; they may well contain `/rc` themselves. */
+const INPUT_LINE = /^[❯>]/;
+
+/** The notification Claude Code prints when it has given up for good. */
+const FAILED_NOTICE = /Remote Control disconnected|Remote Control failed/;
 
 /** The /remote-control status panel — its first entry is "Disconnect this session". */
 const PANEL = /Disconnect this session|(?:Show|Hide) QR code/;
@@ -28,6 +43,13 @@ const MODAL = /(?:❯|›)\s*(?:\d+\.|Yes|No)|Do you want|\(y\/n\)/;
  */
 const FOOTER_LINES = 12;
 
+/**
+ * The indicator sits on the status line, one or two rows from the bottom — a
+ * tighter window than the notifications above it, so that `/rc` typed into the
+ * input box cannot be mistaken for it.
+ */
+const INDICATOR_LINES = 4;
+
 export const DEFAULTS = {
   /** Consecutive checks stuck in "reconnecting" before we treat the bridge as wedged. */
   stuckLimit: 8,
@@ -45,16 +67,34 @@ export function emptyState() {
  * Reduce a captured pane to the handful of signals the rules care about.
  * @param {string} screen raw `tmux capture-pane -p` output
  */
+/**
+ * Read the indicator out of the last few lines.
+ *
+ * Returns 'active' | 'reconnecting' | 'failed', or null when no indicator is on
+ * screen. A truncated `/rc` counts as 'active': the indicator only renders while
+ * a link exists, and reading it as connected merely records the pane and waits,
+ * which is the safe direction.
+ */
+function readIndicator(lines, window = INDICATOR_LINES) {
+  for (const line of lines.slice(Math.max(0, lines.length - window))) {
+    if (INPUT_LINE.test(line.trim())) continue;
+    const m = line.match(RC_INDICATOR);
+    if (m) return m[1] ?? 'active';
+  }
+  return null;
+}
+
 export function readScreen(screen, footerLines = FOOTER_LINES) {
   const lines = String(screen).split('\n');
   const footer = lines.slice(Math.max(0, lines.length - footerLines)).join('\n');
+  const indicator = readIndicator(lines);
 
   return {
     // Signals that make cckeep act are read from the footer only, so text in
     // the conversation cannot trigger anything.
-    connected: footer.includes(CONNECTED),
-    retrying: footer.includes(RETRYING),
-    failed: FAILED.test(footer),
+    connected: indicator === 'active',
+    retrying: indicator === 'reconnecting',
+    failed: indicator === 'failed' || FAILED_NOTICE.test(footer),
 
     // Signals that make cckeep hold off are read from the whole pane. A false
     // positive here costs a skipped pass; missing one costs a keystroke in the