diff --git a/plugins/coderabbit/.codex-plugin/plugin.json b/plugins/coderabbit/.codex-plugin/plugin.json
index 90b90c564..25784c8ae 100644
--- a/plugins/coderabbit/.codex-plugin/plugin.json
+++ b/plugins/coderabbit/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
 {
   "name": "coderabbit",
-  "version": "1.1.1",
+  "version": "1.1.2",
   "description": "AI-powered code review in Codex, powered by CodeRabbit.",
   "author": {
     "name": "CodeRabbit AI",
diff --git a/plugins/coderabbit/skills/coderabbit-review/SKILL.md b/plugins/coderabbit/skills/coderabbit-review/SKILL.md
index eac606bc7..0acdb6500 100644
--- a/plugins/coderabbit/skills/coderabbit-review/SKILL.md
+++ b/plugins/coderabbit/skills/coderabbit-review/SKILL.md
@@ -9,36 +9,41 @@ Use this skill to run CodeRabbit from the terminal, summarize the issues found,
 
 Stay silent while an active review is running. Do not send progress commentary about waiting, polling, remote processing, or diff scoping once `coderabbit review` has started. Only message the user if an authentication step or other prerequisite is needed, when the review completes with results, or when the review has failed or timed out after the full wait window.
 
-## Prerequisites
+## Execution Context and Authentication
 
 1. Confirm the working directory is inside a git repository.
-2. Check the CLI:
-
-```bash
-coderabbit --version
-```
-
-If the command is not found or reports that CodeRabbit is not installed, do not stop at the error. Install it:
-
-```bash
-curl -fsSL https://cli.coderabbit.ai/install.sh | sh
-```
-
-Then re-run `coderabbit --version` to confirm the install succeeded before continuing. After a fresh install, proceed to the authentication step — the user will need to log in.
-
-3. Verify authentication in agent mode:
-
-```bash
-coderabbit auth status --agent
-```
-
-If auth is missing or the CLI reports the user is not authenticated (including right after a fresh install), do not stop at the error. Initiate the login flow:
-
-```bash
-coderabbit auth login --agent
-```
-
-Then re-run `coderabbit auth status --agent` and only continue to review commands after authentication succeeds.
+2. Resolve the trusted, host-installed `coderabbit` executable from the user's
+   normal shell. Do not use a repository- or workspace-controlled executable,
+   alias, or wrapper. Use the resolved absolute path for all commands below.
+3. Run `coderabbit --version`. If no trusted host installation exists, ask the
+   user to install the CLI from <https://www.coderabbit.ai/cli>. Do not install
+   it automatically. Commands below use `coderabbit` for readability; invoke
+   the resolved absolute path.
+
+For local Codex sessions (desktop or CLI, including worktrees), execute the
+resolved CodeRabbit CLI with the harness's command-scoped sandbox escalation so
+that exact process runs on the host with network access. Network permission
+alone is insufficient because it does not expose credentials held by the host
+credential store. Apply the same execution context to `coderabbit review` and
+any reactive authentication command. Do not change global sandbox settings or
+run repository-provided commands outside the sandbox.
+
+Never query, copy, print, or inject a credential from macOS Keychain or another
+host credential store. The trusted CodeRabbit CLI must access its credential
+directly. A Git worktree or repository change does not require a separate login.
+
+Do not proactively check authentication before every review. Start the requested
+review directly. Only after an explicit authentication error, run
+`coderabbit auth status --agent` in the same authoritative execution context.
+If it reports that authentication is missing, ask the user to run
+`coderabbit auth login --agent` in their host terminal. Do not start the login
+flow automatically; retry the review only after the user confirms login
+succeeded.
+
+Codex Cloud and other remote environments cannot reuse a local host credential
+store. In those environments, use only authentication configured inside that
+environment and direct the user to the official CLI documentation when setup is
+required. Never ask the user to paste an API key into the conversation.
 
 ## Review Commands
 
@@ -51,8 +56,9 @@ coderabbit review --agent
 Common narrower scopes:
 
 ```bash
-coderabbit review --agent -t committed
-coderabbit review --agent -t uncommitted
+coderabbit review --agent --committed
+coderabbit review --agent --uncommitted
+coderabbit review --agent --uncommitted --include-untracked
 coderabbit review --agent --base main
 coderabbit review --agent --base-commit <sha>
 ```