Codex/restart from 6f4bb98

[GuthL]

Summary

• Describe the change and the user or maintainer impact.

Validation

• cargo fmt --check
• cargo clippy --all-targets --all-features -- -D warnings
• cargo build --locked
• cargo test --locked
• cargo test --locked --test e2e_cli -- --ignored --test-threads=1
• cargo doc --no-deps

Docs

• README updated if public behavior changed
• docs/ updated if deeper reference material changed
• Screenshots or SVG assets updated if the repo-facing experience changed

Notes

• Call out risks, follow-ups, or release considerations here.

[chatgpt-codex-connector]

💡 Codex Review

KeyClaw/src/proxy/websocket.rs

Line 98 in 89c91ad

match self.rewrite_ws_request_text(text.as_str(), uses_input_only_ws_rewrite(ctx)) {

Offload websocket request rewrites from async worker

In src/proxy/websocket.rs (checked the websocket request path), rewrite_ws_request_text is called directly inside handle_message on the async task, but the new detector stack can invoke OpenAiCompatibleLocalClassifier::accept in src/sensitive.rs, which performs blocking reqwest::blocking network I/O. When the local classifier is enabled (or rewrite work is slow), this blocks a Tokio worker thread and can stall unrelated websocket/proxy traffic; the HTTP handler already avoids this by using spawn_blocking with a timeout.

---

KeyClaw/src/placeholder.rs

Line 94 in 89c91ad

text.char_indices().rev().find_map(|(abs, ch)| {

Reintroduce a bounded scan for partial placeholders

find_partial_placeholder_start now reverse-scans the entire string (text.char_indices().rev()), and this function is called repeatedly from SSE chunk processing (SseStreamResolver::resolve_pending_text). For long input_json_delta streams that keep a placeholder-like tail unresolved, this turns into repeated full-buffer scans and can cause quadratic-time behavior and streaming latency spikes; the previous implementation bounded the scan to a small tail window.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".