@quantiya/codevibe-codex-plugin 2.0.9 → 2.0.11

package/README.md

@@ -48,9 +48,30 @@ install the unified `codevibe --agent` interface yet.
 
 ## How it works
 
-Codex CLI writes session logs to `~/.codex/sessions/` as JSONL files. CodeVibe watches those files with chokidar, parses every log entry, and streams it through E2E-encrypted AWS AppSync to your phone.
-
-Approval prompts (Codex's interactive Y/N confirmations) aren't in the JSONL log, so CodeVibe observes the live tmux pane to detect them — you get real prompts with real options, and your mobile approve/reject is sent back via `tmux send-keys`.
+Codex CLI writes session logs to `~/.codex/sessions/` as JSONL files. A native
+hook supplies the exact rollout path and session id; CodeVibe never guesses log
+ownership from timestamps or working directories, so concurrent sessions in the
+same repository remain isolated. CodeVibe watches that owned log and streams new
+entries through E2E-encrypted AWS AppSync to your phone. Native Codex history is
+never rewritten or deleted. Safety limits keep an unread backlog to its recent
+64 MiB tail and skip an individual record over 16 MiB instead of risking an
+out-of-memory failure.
+
+Approval prompts use Codex's native `PermissionRequest` hook. On macOS and
+qualified native Linux, a live tmux-pane observer is also a fallback for prompt
+formats absent from hooks; mobile approve/reject is sent back via `tmux send-keys`.
+The pane fallback fails closed on WSL until its filesystem boundary is qualified;
+hook-based prompts and ordinary mobile control remain available there.
+
+The transient tmux mirror lives in a private random `0700` directory with
+exclusive `0600` data and writer-state files. Its writer independently stops at
+16 MiB and confirms quiescence before CodeVibe truncates or removes the files.
+If quiescence cannot be confirmed, the linked, bounded files are retained for
+writer-aware cleanup rather than unlinked beneath a live writer. The observer
+will not allocate another mirror while that exact generation is unconfirmed;
+once it reports `done`, the same owner safely reaps it. Completed crash
+leftovers from dead owners are reaped after seven days. The mirror is a prompt
+detector, not conversation storage.
 
 Each live Codex process appears as its own session on your phone, so you can run multiple concurrent Codex sessions side-by-side with Claude and Antigravity.