From b5cb26e7e4a72bd30c05117c3fc823242cfbfe75 Mon Sep 17 00:00:00 2001 From: murashit Date: Mon, 18 May 2026 12:05:04 +0900 Subject: [PATCH] Document rewrite selection popover behavior --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6a7d9206..993d4690 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ Rolling back a turn only removes the latest Codex turn from thread history and r Codex configuration stays in Codex. Defaults and runtime policy, including model, reasoning effort, sandboxing, approvals, MCP servers, hook definitions, network access, and providers, should be configured the same way you configure Codex CLI. -The settings tab stores only panel-specific preferences: Codex executable path, composer send shortcut, and optional model/effort overrides for automatic thread naming. Model and reasoning effort controls in the panel are temporary inputs for subsequent turns, not saved Codex defaults. +The settings tab stores only panel-specific preferences: Codex executable path, composer send shortcut, and optional model/effort overrides for automatic thread naming and selection rewrites. Model and reasoning effort controls in the panel are temporary inputs for subsequent turns, not saved Codex defaults. The status dot opens connection controls and diagnostics, including effective config and usage limits. The settings tab can load app-server-backed hook status and archived threads on demand, including hook trust and enabled state. Codex Panel can show and request those app-server operations, but it does not edit or duplicate Codex config.