ring-cli 0.9.0__tar.gz → 0.11.0__tar.gz

{ring_cli-0.9.0 → ring_cli-0.11.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ring-cli
-Version: 0.9.0
+Version: 0.11.0
 Summary: RiNG — Realtime Instance Notification Grid for active agent CLI sessions.
 Keywords: claude-code,codex,tui,dashboard,session,monitor,rich
 Author: Wei Lee
@@ -59,6 +59,7 @@ RiNG puts them on one board, with sessions waiting for you sorted first.
 - **Waiting first**: sessions that need your response are highlighted and sorted above the rest.
 - **Jump back to the terminal**: in the TUI, select a session and press `Enter` / `Space` to focus tmux, iTerm2, Terminal.app (macOS), or a Linux X11 window (`wmctrl`).
 - **Notifies you without the board open**: with hooks installed, the moment a session turns 🔴 waiting it beeps and fires a system notification — even with no RiNG board running. With `terminal-notifier`, clicking the notification jumps back.
+- **Reply to permission requests in place**: with the cursor on a 🔴 waiting row, press `p` — RiNG reads the permission dialog from that session's terminal screen, pops the numbered options in a modal, and presses your choice for you, so you don't have to jump over one by one (sessions inside tmux, plus plain iTerm2 tabs on macOS).
 - **Name your sessions**: press `n` in the TUI to name a session, e.g. "auth refactor"; once named, the board and notifications show the name instead of the workspace directory.
 - **See what it is waiting for**: in hook mode, a 🔴 waiting session carries the concrete pending item (the command to run, the question asked) — shown in the TUI and in the notification body.
 - **Fits your status bar**: `ring --format oneline` prints a `🔴2 🟢1 🟡3` one-liner for tmux / SwiftBar / waybar; `--format json` feeds scripts.
@@ -153,7 +154,7 @@ Completes subcommands, flags, and `config set` keys; `ring focus` prompts for a
 ## Watch Mode
 
 - With **Textual** (`[tui]` extra) in a real terminal: interactive TUI.
-  Use `↑/↓` to select, `Enter` / `Space` to jump, `n` to name a session, `a` to toggle ended sessions, `dd` to hide a session (it reappears automatically once it has new activity), `r` to refresh, and `q` to quit.
+  Use `↑/↓` to select, `Enter` / `Space` to jump, `p` to reply to a permission request in place, `n` to name a session, `a` to toggle ended sessions, `dd` to hide a session (it reappears automatically once it has new activity), `r` to refresh, and `q` to quit.
   If you have vim muscle memory like I do, `j/k` move up/down and `g/G` jump to the first/last row.
   When the selected row is 🔴 waiting, a line under the table shows **what it is concretely waiting for** (the command to run, the question asked; hook mode only).
 - Otherwise: Rich polling; without Rich, plain text.
@@ -172,6 +173,30 @@ hands the request to the TUI so it selects that session; otherwise it focuses th
 TTY matching is most accurate in hook mode. Without hooks, Codex falls back to zero-config matching:
 one live Codex session per cwd can jump correctly; multiple live Codex sessions in the same cwd are shown conservatively to avoid focusing the wrong tab.
 
+### Reply To Permission Requests In Place (`p`)
+
+With the cursor on a 🔴 waiting row, press `p`. RiNG reads that session's screen, parses the
+permission dialog (Claude Code's "Do you want to proceed?" box, including background-subagent
+ones with a "from the … agent" header), and lists the numbered options verbatim in a modal.
+After you pick one, RiNG **captures the screen again** to confirm the dialog is still there and
+unchanged (it may have been answered while you were deciding), only then sends that single
+digit, and re-checks that the dialog actually disappeared.
+
+- **Sessions inside tmux**: reads the screen with `tmux capture-pane` and sends keys with
+  `tmux send-keys`.
+- **Sessions in a plain iTerm2 tab on macOS** (no tmux): locates the matching iTerm2 session by
+  its `tty` via AppleScript, and both reads the screen and sends keys through `osascript`. The
+  first use triggers the macOS Automation permission prompt ("allow control of iTerm2") — allow
+  it once.
+
+Safety first: if no recognizable dialog can be parsed (missing markers, numbering, or cursor),
+RiNG only shows a toast and **never sends a key** — without the dialog, keystrokes would land in
+the chat input box as text. If the dialog happens to vanish in the instant the digit is sent and
+the digit lands in the input box, RiNG sends a Backspace to clean it up and warns you.
+
+**Limits**: reading the screen requires a tmux pane coordinate, or (on macOS) an iTerm2 session
+with a detectable tty; for other sessions, press `Enter` to jump over and reply there.
+
 ### Notifications
 
 Default behavior: with hooks installed, the moment a session changes to 🔴 waiting, the hook beeps
@@ -336,8 +361,14 @@ RiNG prefers clickable `terminal-notifier`, then falls back to `osascript` on ma
 on Linux. If none are available, RiNG keeps the board running and skips notifications.
 
 Config keys include `notify_sound`, `notify_sound_name`, `notify_ignore_dnd`,
-`notify_repeat_seconds`, `notify_repeat_max`, and `notify_backend`. Custom notification channels
-can be added by registering another `Notifier`.
+`notify_repeat_seconds`, `notify_repeat_max`, `notify_backend`, and `waiting_cooldown_seconds`.
+Custom notification channels can be added by registering another `Notifier`.
+
+Background subagent permission requests can make a session flap between waiting and working in
+quick succession. `waiting_cooldown_seconds` (180s by default) stops `ring hook`'s system
+notification and the TUI's bell/reminder from firing again the instant a session re-enters waiting
+within the cooldown window of its last alert; set it to `0` to disable the cooldown (alert on
+every re-entry, the old behavior).
 
 `agent-hooks` is an optional external hook helper / decision UI. If it is installed and
 `notify_backend = "agent-hooks"`, `ring hook` still writes RiNG registry state, then passes the
@@ -372,6 +403,7 @@ notify_ignore_dnd = false
 notify_backend = "auto"          # auto / terminal-notifier / osascript / notify-send / agent-hooks / none
 notify_repeat_seconds = [30, 120, 300]
 notify_repeat_max = 3
+waiting_cooldown_seconds = 180   # suppress an immediate re-alert on re-entering waiting within this window; 0 = off
 notify_ntfy_url = ""             # full ntfy topic URL enables phone push (e.g. https://ntfy.sh/my-topic)
 notify_webhook_url = ""          # URL enables the generic webhook backend (JSON POST)
 notify_also = []                 # extra backends fired besides the primary, e.g. ["ntfy"]

{ring_cli-0.9.0 → ring_cli-0.11.0}/README.en.md

@@ -34,6 +34,7 @@ RiNG puts them on one board, with sessions waiting for you sorted first.
 - **Waiting first**: sessions that need your response are highlighted and sorted above the rest.
 - **Jump back to the terminal**: in the TUI, select a session and press `Enter` / `Space` to focus tmux, iTerm2, Terminal.app (macOS), or a Linux X11 window (`wmctrl`).
 - **Notifies you without the board open**: with hooks installed, the moment a session turns 🔴 waiting it beeps and fires a system notification — even with no RiNG board running. With `terminal-notifier`, clicking the notification jumps back.
+- **Reply to permission requests in place**: with the cursor on a 🔴 waiting row, press `p` — RiNG reads the permission dialog from that session's terminal screen, pops the numbered options in a modal, and presses your choice for you, so you don't have to jump over one by one (sessions inside tmux, plus plain iTerm2 tabs on macOS).
 - **Name your sessions**: press `n` in the TUI to name a session, e.g. "auth refactor"; once named, the board and notifications show the name instead of the workspace directory.
 - **See what it is waiting for**: in hook mode, a 🔴 waiting session carries the concrete pending item (the command to run, the question asked) — shown in the TUI and in the notification body.
 - **Fits your status bar**: `ring --format oneline` prints a `🔴2 🟢1 🟡3` one-liner for tmux / SwiftBar / waybar; `--format json` feeds scripts.
@@ -128,7 +129,7 @@ Completes subcommands, flags, and `config set` keys; `ring focus` prompts for a
 ## Watch Mode
 
 - With **Textual** (`[tui]` extra) in a real terminal: interactive TUI.
-  Use `↑/↓` to select, `Enter` / `Space` to jump, `n` to name a session, `a` to toggle ended sessions, `dd` to hide a session (it reappears automatically once it has new activity), `r` to refresh, and `q` to quit.
+  Use `↑/↓` to select, `Enter` / `Space` to jump, `p` to reply to a permission request in place, `n` to name a session, `a` to toggle ended sessions, `dd` to hide a session (it reappears automatically once it has new activity), `r` to refresh, and `q` to quit.
   If you have vim muscle memory like I do, `j/k` move up/down and `g/G` jump to the first/last row.
   When the selected row is 🔴 waiting, a line under the table shows **what it is concretely waiting for** (the command to run, the question asked; hook mode only).
 - Otherwise: Rich polling; without Rich, plain text.
@@ -147,6 +148,30 @@ hands the request to the TUI so it selects that session; otherwise it focuses th
 TTY matching is most accurate in hook mode. Without hooks, Codex falls back to zero-config matching:
 one live Codex session per cwd can jump correctly; multiple live Codex sessions in the same cwd are shown conservatively to avoid focusing the wrong tab.
 
+### Reply To Permission Requests In Place (`p`)
+
+With the cursor on a 🔴 waiting row, press `p`. RiNG reads that session's screen, parses the
+permission dialog (Claude Code's "Do you want to proceed?" box, including background-subagent
+ones with a "from the … agent" header), and lists the numbered options verbatim in a modal.
+After you pick one, RiNG **captures the screen again** to confirm the dialog is still there and
+unchanged (it may have been answered while you were deciding), only then sends that single
+digit, and re-checks that the dialog actually disappeared.
+
+- **Sessions inside tmux**: reads the screen with `tmux capture-pane` and sends keys with
+  `tmux send-keys`.
+- **Sessions in a plain iTerm2 tab on macOS** (no tmux): locates the matching iTerm2 session by
+  its `tty` via AppleScript, and both reads the screen and sends keys through `osascript`. The
+  first use triggers the macOS Automation permission prompt ("allow control of iTerm2") — allow
+  it once.
+
+Safety first: if no recognizable dialog can be parsed (missing markers, numbering, or cursor),
+RiNG only shows a toast and **never sends a key** — without the dialog, keystrokes would land in
+the chat input box as text. If the dialog happens to vanish in the instant the digit is sent and
+the digit lands in the input box, RiNG sends a Backspace to clean it up and warns you.
+
+**Limits**: reading the screen requires a tmux pane coordinate, or (on macOS) an iTerm2 session
+with a detectable tty; for other sessions, press `Enter` to jump over and reply there.
+
 ### Notifications
 
 Default behavior: with hooks installed, the moment a session changes to 🔴 waiting, the hook beeps
@@ -311,8 +336,14 @@ RiNG prefers clickable `terminal-notifier`, then falls back to `osascript` on ma
 on Linux. If none are available, RiNG keeps the board running and skips notifications.
 
 Config keys include `notify_sound`, `notify_sound_name`, `notify_ignore_dnd`,
-`notify_repeat_seconds`, `notify_repeat_max`, and `notify_backend`. Custom notification channels
-can be added by registering another `Notifier`.
+`notify_repeat_seconds`, `notify_repeat_max`, `notify_backend`, and `waiting_cooldown_seconds`.
+Custom notification channels can be added by registering another `Notifier`.
+
+Background subagent permission requests can make a session flap between waiting and working in
+quick succession. `waiting_cooldown_seconds` (180s by default) stops `ring hook`'s system
+notification and the TUI's bell/reminder from firing again the instant a session re-enters waiting
+within the cooldown window of its last alert; set it to `0` to disable the cooldown (alert on
+every re-entry, the old behavior).
 
 `agent-hooks` is an optional external hook helper / decision UI. If it is installed and
 `notify_backend = "agent-hooks"`, `ring hook` still writes RiNG registry state, then passes the
@@ -347,6 +378,7 @@ notify_ignore_dnd = false
 notify_backend = "auto"          # auto / terminal-notifier / osascript / notify-send / agent-hooks / none
 notify_repeat_seconds = [30, 120, 300]
 notify_repeat_max = 3
+waiting_cooldown_seconds = 180   # suppress an immediate re-alert on re-entering waiting within this window; 0 = off
 notify_ntfy_url = ""             # full ntfy topic URL enables phone push (e.g. https://ntfy.sh/my-topic)
 notify_webhook_url = ""          # URL enables the generic webhook backend (JSON POST)
 notify_also = []                 # extra backends fired besides the primary, e.g. ["ntfy"]

{ring_cli-0.9.0 → ring_cli-0.11.0}/pyproject.toml

@@ -2,7 +2,7 @@
 # import 的 module（見 [tool.uv.build-backend] module-name）與 CLI 指令仍是 `ring`。
 [project]
 name = "ring-cli"
-version = "0.9.0"
+version = "0.11.0"
 description = "RiNG — Realtime Instance Notification Grid for active agent CLI sessions."
 readme = "README.en.md"
 requires-python = ">=3.13"

{ring_cli-0.9.0 → ring_cli-0.11.0}/src/ring/config.py

@@ -20,6 +20,8 @@
                                       #   "none" = 完全不發通知（RiNG 當純看板）
     notify_repeat_seconds = [30, 120, 300]  # 持續等你時，多久後重複提醒
     notify_repeat_max = 3             # 重複提醒上限；0 = 不限
+    waiting_cooldown_seconds = 180    # session 離開 WAITING 又轉回時，距上次提醒未滿這段時間就
+                                      #   不再當「新轉入」立即提醒（防翻轉轟炸）；0 = 關閉（現行為）
     notify_ntfy_url = "https://ntfy.sh/my-topic"   # 設了才啟用 ntfy 後端（推到手機）
     notify_webhook_url = "https://example.com/hook"  # 設了才啟用 webhook 後端（JSON POST）
     notify_also = ["ntfy"]            # 主後端之外「加發」的後端（例如桌面通知＋手機各一份）
@@ -69,6 +71,7 @@ class Config:
     notify_backend: str = "auto"
     notify_repeat_seconds: tuple[int, ...] = (30, 120, 300)
     notify_repeat_max: int = 3  # 0 = 不限
+    waiting_cooldown_seconds: int = 180  # 離開 WAITING 又轉回時的提醒冷卻期；0 = 關閉（現行為）
     notify_ntfy_url: str = ""  # 完整 ntfy topic URL；空＝ntfy 後端不可用
     notify_webhook_url: str = ""  # webhook URL；空＝webhook 後端不可用
     notify_also: tuple[str, ...] = ()  # 主後端之外加發的後端名（如 ["ntfy"]）
@@ -138,6 +141,7 @@ def load(path: Path | None = None) -> Config:
         notify_ignore_dnd=_as_bool(raw.get("notify_ignore_dnd"), d.notify_ignore_dnd),
         notify_repeat_seconds=_as_positive_int_tuple(raw.get("notify_repeat_seconds"), d.notify_repeat_seconds),
         notify_repeat_max=max(0, _as_int(raw.get("notify_repeat_max"), d.notify_repeat_max)),
+        waiting_cooldown_seconds=max(0, _as_int(raw.get("waiting_cooldown_seconds"), d.waiting_cooldown_seconds)),
         notify_backend=notify_backend,
         notify_ntfy_url=(raw["notify_ntfy_url"] if isinstance(raw.get("notify_ntfy_url"), str) else ""),
         notify_webhook_url=(raw["notify_webhook_url"] if isinstance(raw.get("notify_webhook_url"), str) else ""),
@@ -208,6 +212,7 @@ _SETTERS: dict[str, Callable[[str], object]] = {
     "notify_backend": str,
     "notify_repeat_seconds": _coerce_int_list,
     "notify_repeat_max": _coerce_int,
+    "waiting_cooldown_seconds": _coerce_int,
     "notify_ntfy_url": str,
     "notify_webhook_url": str,
     "notify_also": _coerce_str_list,

{ring_cli-0.9.0 → ring_cli-0.11.0}/src/ring/hook.py

@@ -169,7 +169,8 @@ def _record_session_state(data: dict[str, Any], selected_provider: str) -> None:
 
     unhide_session(event.session_id)
     path = RING_REGISTRY / f"{quote(event.session_id, safe=':')}.json"
-    prev_status = _previous_status(path)
+    prev_row = _previous_row(path)
+    prev_status = str(prev_row["status"]) if "status" in prev_row else None
     if event.status is Status.ENDED:
         path.unlink(missing_ok=True)  # 乾淨離場：直接消失
         if prev_status is not None and prev_status != Status.ENDED.value:
@@ -213,6 +214,19 @@ def _record_session_state(data: dict[str, Any], selected_provider: str) -> None:
     if tty:
         payload["tty"] = tty
 
+    # waiting 通知冷卻（防翻轉轟炸）：hook 是短命 process，冷卻狀態持久化在 registry row
+    # 的 waiting_notified_at（上次 waiting 通知的 epoch 時間戳）。離開 WAITING 也要把時間戳
+    # 帶進新 row（payload 每次重建，不帶會遺失），快速翻回 WAITING 時才判得出「還在冷卻期」。
+    # 舊 row 沒這欄位 = 從未通知過 → 照發。並發寫沿用既有 tmp+replace 的 last-write-wins。
+    last_notified = _as_epoch(prev_row.get("waiting_notified_at"))
+    if last_notified is not None:
+        payload["waiting_notified_at"] = last_notified
+    should_ring = False
+    if event.status is Status.WAITING:
+        should_ring = _waiting_ring_allowed(last_notified, now)
+        if should_ring:
+            payload["waiting_notified_at"] = now
+
     RING_REGISTRY.mkdir(parents=True, exist_ok=True)
     tmp = path.with_suffix(".json.tmp")
     tmp.write_text(json.dumps(payload))
@@ -221,17 +235,35 @@ def _record_session_state(data: dict[str, Any], selected_provider: str) -> None:
     if prev_status != event.status.value:
         log_transition(event.session_id, event.provider, event.cwd, event.status.value)
 
-    if event.status is Status.WAITING:
+    if should_ring:
         _ring_waiting_now(event, payload, last_action)
 
 
-def _previous_status(path: Path) -> str | None:
-    """讀 registry 檔目前的狀態值（給轉換偵測用）；沒檔 / 壞檔回 None。"""
+def _previous_row(path: Path) -> dict[str, Any]:
+    """讀 registry 檔目前的內容（給轉換偵測與通知冷卻用）；沒檔 / 壞檔回空 dict。"""
     try:
         data = json.loads(path.read_text())
-        return str(data["status"])
+        return data if isinstance(data, dict) else {}
     except Exception:
-        return None
+        return {}
+
+
+def _as_epoch(v: Any) -> float | None:
+    """把 row 欄位值安全轉成 epoch float；缺欄位 / 型別不對回 None（視為從未通知）。"""
+    return float(v) if isinstance(v, (int, float)) and not isinstance(v, bool) else None
+
+
+def _waiting_ring_allowed(last_notified: float | None, now: float) -> bool:
+    """hook 的 waiting 通知是否放行：距上次通知未滿 ``waiting_cooldown_seconds`` 就不發。
+
+    背景 subagent 的權限請求會讓 session 以 30 秒～2 分鐘頻率在 working↔waiting 間翻轉，
+    每次轉入都發一則系統通知會轟炸使用者。cooldown=0 = 關閉（維持現行為：每次轉入都發）；
+    從未通知過（``last_notified`` 為 None，含舊版 row 沒有該欄位）一律放行。
+    """
+    cooldown = get_config().waiting_cooldown_seconds
+    if cooldown <= 0 or last_notified is None:
+        return True
+    return now - last_notified >= cooldown
 
 
 def _ring_waiting_now(event: Any, payload: dict[str, Any], last_action: str) -> None:

{ring_cli-0.9.0 → ring_cli-0.11.0}/src/ring/locale/en/LC_MESSAGES/ring.po

@@ -653,3 +653,42 @@ msgstr "total wait"
 
 msgid "⚠️ 其中 {n} 段還在 🔴 等你（計到現在為止）。"
 msgstr "⚠️ {n} of these are still 🔴 waiting for you (counted up to now)."
+
+msgid "回覆權限"
+msgstr "reply perm"
+
+msgid "回覆 {project} 的權限請求"
+msgstr "Reply to the permission request from {project}"
+
+msgid "Enter 或數字鍵送出、Esc 取消"
+msgstr "Enter or a digit key sends, Esc cancels"
+
+msgid "{project}：沒有 tmux 座標，且非 macOS 上的 iTerm2 session，無法就地回覆"
+msgstr "{project}: no tmux coordinates, and not a macOS iTerm2 session either — cannot reply in place"
+
+msgid "{project}：讀不到 {backend} 畫面"
+msgstr "{project}: cannot read the {backend} screen"
+
+msgid "{project}：畫面上沒有可辨識的權限對話框，未送出任何按鍵"
+msgstr "{project}: no recognizable permission dialog on screen; no key was sent"
+
+msgid "→ {project}：已回覆權限（{option}）"
+msgstr "→ {project}: permission answered ({option})"
+
+msgid "{project}：權限對話框已不在，未送出任何按鍵"
+msgstr "{project}: the permission dialog is gone; no key was sent"
+
+msgid "{project}：對話框內容已變化，未送出；請再按一次 p"
+msgstr "{project}: the dialog changed; nothing sent — press p again"
+
+msgid "{project}：tmux send-keys 失敗，沒能回覆"
+msgstr "{project}: tmux send-keys failed; could not reply"
+
+msgid "{project}：已送出但對話框還在，請跳過去確認"
+msgstr "{project}: key sent but the dialog is still there — jump over to check"
+
+msgid "{project}：對話框已不在，數字落進輸入框，已補 Backspace 清掉"
+msgstr "{project}: the dialog was gone and the digit landed in the input box — sent Backspace to clean it up"
+
+msgid "{project}：已送出但拿不到畫面驗證，請跳過去確認"
+msgstr "{project}: key sent but the screen could not be re-read to verify — jump over to check"

{ring_cli-0.9.0 → ring_cli-0.11.0}/src/ring/locale/ring.pot

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: PROJECT VERSION\n"
 "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2026-07-10 15:32+0800\n"
+"POT-Creation-Date: 2026-07-12 09:22+0800\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -52,7 +52,7 @@ msgstr[1] ""
 msgid "🎤 RiNG — {sess} · {proc}"
 msgstr ""
 
-#: src/ring/cli.py:163 src/ring/cli.py:216 src/ring/tui.py:213
+#: src/ring/cli.py:163 src/ring/cli.py:216 src/ring/tui.py:274
 msgid "圖例"
 msgstr ""
 
@@ -63,32 +63,32 @@ msgstr ""
 #: src/ring/cli.py:184 src/ring/cli.py:338 src/ring/commands/doctor.py:31
 #: src/ring/commands/doctor.py:68 src/ring/commands/doctor.py:70
 #: src/ring/commands/doctor.py:72 src/ring/commands/doctor.py:134
-#: src/ring/tui.py:168
+#: src/ring/tui.py:229
 msgid "狀態"
 msgstr ""
 
-#: src/ring/cli.py:186 src/ring/cli.py:235 src/ring/tui.py:170
+#: src/ring/cli.py:186 src/ring/cli.py:235 src/ring/tui.py:231
 msgid "工具"
 msgstr ""
 
 #: src/ring/cli.py:187 src/ring/cli.py:235 src/ring/commands/stats.py:60
-#: src/ring/tui.py:171
+#: src/ring/tui.py:232
 msgid "專案"
 msgstr ""
 
-#: src/ring/cli.py:188 src/ring/cli.py:235 src/ring/tui.py:171
+#: src/ring/cli.py:188 src/ring/cli.py:235 src/ring/tui.py:232
 msgid "進度"
 msgstr ""
 
-#: src/ring/cli.py:189 src/ring/cli.py:235 src/ring/tui.py:171
+#: src/ring/cli.py:189 src/ring/cli.py:235 src/ring/tui.py:232
 msgid "閒置"
 msgstr ""
 
-#: src/ring/cli.py:190 src/ring/cli.py:235 src/ring/tui.py:171
+#: src/ring/cli.py:190 src/ring/cli.py:235 src/ring/tui.py:232
 msgid "去哪"
 msgstr ""
 
-#: src/ring/cli.py:192 src/ring/cli.py:235 src/ring/tui.py:171
+#: src/ring/cli.py:192 src/ring/cli.py:235 src/ring/tui.py:232
 msgid "動作"
 msgstr ""
 
@@ -305,41 +305,41 @@ msgstr ""
 msgid "重開 Codex session、並在它詢問時「信任」這個 hook，🔴 等你狀態才會精準起來（Codex 不會執行未信任的 hook）。"
 msgstr ""
 
-#: src/ring/hook.py:406
+#: src/ring/hook.py:438
 #, python-brace-format
 msgid "⚠️ 偵測到其他工具也掛在 {events}：{cmds}"
 msgstr ""
 
-#: src/ring/hook.py:407
+#: src/ring/hook.py:439
 msgid "它們會跟 RiNG 的通知重複觸發；要完全改用 RiNG，建議移除它們。"
 msgstr ""
 
-#: src/ring/hook.py:455 src/ring/hook.py:531
+#: src/ring/hook.py:487 src/ring/hook.py:563
 #, python-brace-format
 msgid "⚠️ {path} 不是合法 JSON，先處理它再來。"
 msgstr ""
 
-#: src/ring/hook.py:493
+#: src/ring/hook.py:525
 #, python-brace-format
 msgid "✅ RiNG hooks 已經裝過了，沒有變更。（{path}）"
 msgstr ""
 
-#: src/ring/hook.py:506
+#: src/ring/hook.py:538
 #, python-brace-format
 msgid "✅ 已註冊 RiNG hooks（{events}）到 {path}"
 msgstr ""
 
-#: src/ring/hook.py:525
+#: src/ring/hook.py:557
 #, python-brace-format
 msgid "ℹ️ {path} 不存在，沒有可移除的 hook。"
 msgstr ""
 
-#: src/ring/hook.py:552
+#: src/ring/hook.py:584
 #, python-brace-format
 msgid "ℹ️ 沒有找到 RiNG hook 條目，無需移除。（{path}）"
 msgstr ""
 
-#: src/ring/hook.py:556
+#: src/ring/hook.py:588
 #, python-brace-format
 msgid "✅ 已移除 RiNG hooks（{events}）從 {path}"
 msgstr ""
@@ -349,103 +349,167 @@ msgstr ""
 msgid "⚠️ ring plugin '{name}' 載入失敗：{error}"
 msgstr ""
 
-#: src/ring/tui.py:88
+#: src/ring/tui.py:91
 #, python-brace-format
 msgid "為 {project} 命名（Enter 存、Esc 取消、清空移除）"
 msgstr ""
 
-#: src/ring/tui.py:89
+#: src/ring/tui.py:92
 msgid "這個 session 在做什麼…"
 msgstr ""
 
-#: src/ring/tui.py:106
+#: src/ring/tui.py:136
+#, python-brace-format
+msgid "回覆 {project} 的權限請求"
+msgstr ""
+
+#: src/ring/tui.py:141
+msgid "Enter 或數字鍵送出、Esc 取消"
+msgstr ""
+
+#: src/ring/tui.py:164
 msgid "離場"
 msgstr ""
 
-#: src/ring/tui.py:107
+#: src/ring/tui.py:165
 msgid "刷新"
 msgstr ""
 
-#: src/ring/tui.py:108
+#: src/ring/tui.py:166
 msgid "含已離場"
 msgstr ""
 
-#: src/ring/tui.py:109
+#: src/ring/tui.py:167
 msgid "命名"
 msgstr ""
 
-#: src/ring/tui.py:110
+#: src/ring/tui.py:168
 msgid "隱藏"
 msgstr ""
 
-#: src/ring/tui.py:111
+#: src/ring/tui.py:169
 msgid "最久等待"
 msgstr ""
 
-#: src/ring/tui.py:112 src/ring/tui.py:113
+#: src/ring/tui.py:170
+msgid "回覆權限"
+msgstr ""
+
+#: src/ring/tui.py:171 src/ring/tui.py:172
 msgid "跳過去"
 msgstr ""
 
-#: src/ring/tui.py:189
+#: src/ring/tui.py:250
 msgid "💡 同專案開了多個 session，裝 hook 跳轉才精準：ring install-hooks"
 msgstr ""
 
-#: src/ring/tui.py:191
+#: src/ring/tui.py:252
 msgid "↑/↓ 選一列，Enter 或 Space 跳到那個 session 的終端"
 msgstr ""
 
-#: src/ring/tui.py:227
+#: src/ring/tui.py:288
 #, python-brace-format
 msgid "🔔 {names} 在等你回話"
 msgstr ""
 
-#: src/ring/tui.py:268
+#: src/ring/tui.py:329
 #, python-brace-format
 msgid "→ 已跳到 {project}（來自通知）"
 msgstr ""
 
-#: src/ring/tui.py:273
+#: src/ring/tui.py:334
 msgid "那個 session 已不在場"
 msgstr ""
 
-#: src/ring/tui.py:332
+#: src/ring/tui.py:393
 msgid "  ⚠ hook 可能失效：來源檔有更新但沒有 heartbeat"
 msgstr ""
 
-#: src/ring/tui.py:361 src/ring/tui.py:385 src/ring/tui.py:411
+#: src/ring/tui.py:422 src/ring/tui.py:446 src/ring/tui.py:479
+#: src/ring/tui.py:544
 msgid "（沒有選到 session）"
 msgstr ""
 
-#: src/ring/tui.py:392
+#: src/ring/tui.py:453
 #, python-brace-format
 msgid "→ {project}（{where}）"
 msgstr ""
 
-#: src/ring/tui.py:394
+#: src/ring/tui.py:455
 #, python-brace-format
 msgid "{project}：{msg}"
 msgstr ""
 
-#: src/ring/tui.py:402
+#: src/ring/tui.py:463
 msgid "（沒有正在等待的 session）"
 msgstr ""
 
-#: src/ring/tui.py:419
+#: src/ring/tui.py:486
+#, python-brace-format
+msgid "{project}：沒有 tmux 座標，且非 macOS 上的 iTerm2 session，無法就地回覆"
+msgstr ""
+
+#: src/ring/tui.py:493
+#, python-brace-format
+msgid "{project}：讀不到 {backend} 畫面"
+msgstr ""
+
+#: src/ring/tui.py:497
+#, python-brace-format
+msgid "{project}：畫面上沒有可辨識的權限對話框，未送出任何按鍵"
+msgstr ""
+
+#: src/ring/tui.py:526
+#, python-brace-format
+msgid "→ {project}：已回覆權限（{option}）"
+msgstr ""
+
+#: src/ring/tui.py:530
+#, python-brace-format
+msgid "{project}：權限對話框已不在，未送出任何按鍵"
+msgstr ""
+
+#: src/ring/tui.py:531
+#, python-brace-format
+msgid "{project}：對話框內容已變化，未送出；請再按一次 p"
+msgstr ""
+
+#: src/ring/tui.py:532
+#, python-brace-format
+msgid "{project}：tmux send-keys 失敗，沒能回覆"
+msgstr ""
+
+#: src/ring/tui.py:533
+#, python-brace-format
+msgid "{project}：已送出但對話框還在，請跳過去確認"
+msgstr ""
+
+#: src/ring/tui.py:535
+#, python-brace-format
+msgid "{project}：對話框已不在，數字落進輸入框，已補 Backspace 清掉"
+msgstr ""
+
+#: src/ring/tui.py:537
+#, python-brace-format
+msgid "{project}：已送出但拿不到畫面驗證，請跳過去確認"
+msgstr ""
+
+#: src/ring/tui.py:552
 #, python-brace-format
 msgid "再按一次 d 隱藏 {project}（有新活動會自動重新出現）"
 msgstr ""
 
-#: src/ring/tui.py:424
+#: src/ring/tui.py:557
 #, python-brace-format
 msgid "{project} 是仍在執行的 process，無法隱藏；請跳過去結束它"
 msgstr ""
 
-#: src/ring/tui.py:432
+#: src/ring/tui.py:565
 #, python-brace-format
 msgid "已隱藏 {project}，並清掉 RiNG 狀態；有新活動會自動重新出現"
 msgstr ""
 
-#: src/ring/tui.py:434
+#: src/ring/tui.py:567
 #, python-brace-format
 msgid "已隱藏 {project}（沒有 RiNG registry 可清；有新活動會自動重新出現）"
 msgstr ""