You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a2c8b38
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs-site/src/content/docs/reference/configuration.md
+27-11Lines changed: 27 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -187,7 +187,8 @@ network. Only do this on trusted networks, and always set a strong `OPENCODEX_AP
187
187
|`location?`|`string`| Vertex location; environment fallback is `GOOGLE_CLOUD_LOCATION`. |
188
188
|`mcpServers?`|`Record<string,CursorMcpServerConfig>`|**Cursor only.** MCP servers started over stdio or reached over Streamable HTTP; fields are listed below. |
189
189
|`desktopExecutor?`|`DesktopExecutorConfig`|**Cursor only.** External computer-use/record-screen commands; fields are listed below. |
190
-
|`unsafeAllowNativeLocalExec?`|`boolean`|**Cursor adapter only.** Opt-in escape hatch for Cursor server-driven local `read` / `write` / `delete` / `ls` / `grep` / `shell` / `fetch` execution. Defaults to `false` so remote Cursor messages cannot bypass Codex approval and sandbox enforcement. See [Cursor provider](#cursor-provider-adapter-cursor) below. |
190
+
|`unsafeAllowNativeLocalExec?`|`boolean`|**Cursor adapter only.** Legacy compatibility boolean for the Cursor server-driven local `read` / `write` / `delete` / `ls` / `grep` / `shell` / `fetch` executor. Equivalent to `nativeLocalExec: "on"` when `nativeLocalExec` is unset; an explicit `nativeLocalExec` value always wins. Defaults to `false`. Prefer `nativeLocalExec` for new configs. See [Cursor provider](#cursor-provider-adapter-cursor) below. |
191
+
|`nativeLocalExec?`|`"off" \| "codex-sandbox" \| "on"`|**Cursor adapter only.** Native local exec policy for the Cursor server-driven executor. `"off"` (default) rejects it; `"on"` is the trusted-local opt-in; `"codex-sandbox"` is accepted for backwards compatibility but is fail-closed like `"off"`. See [Cursor provider](#cursor-provider-adapter-cursor) below. |
191
192
192
193
For broken `openai-responses` compatibility gateways, `responsesItemIdRepair` belongs on the
193
194
provider object itself, for example:
@@ -232,9 +233,17 @@ the selection is preserved on every request. They remain available when live mod
232
233
`default`, just like the original `cursor/auto` entry.
233
234
234
235
By default, Cursor's server-driven native local tools stay **disabled**. Codex keeps using its own
235
-
tools (`apply_patch`, `exec_command`, and so on) with approval and sandbox policy. Set
236
-
`unsafeAllowNativeLocalExec` only for trusted local experiments where you accept that Cursor may
237
-
read, write, delete, list, grep, shell, or fetch on your machine **without** Codex's approval path.
236
+
tools (`apply_patch`, `exec_command`, and so on) with approval and sandbox policy. Use the
237
+
`nativeLocalExec` field to choose a policy:
238
+
239
+
-**`"off"` (default, safest)** — rejects all Cursor server-driven local `read`, `write`, `delete`,
240
+
`ls`, `grep`, `shell`, and `fetch` execution. Use this unless you have deliberately opted in.
241
+
-**`"on"` (trusted-local opt-in)** — always allows Cursor-native local execution for this provider.
242
+
Use it only for a trusted local experiment on a host where every data-plane caller is trusted.
243
+
-**`"codex-sandbox"` (accepted, fail-closed)** — recognized for backwards compatibility, but
244
+
currently behaves like `"off"`. Responses `instructions` / `system` / `developer` text is
245
+
caller-controlled prose, and opencodex has no trustworthy per-request attestation that it reflects
246
+
a real Codex sandbox state, so it never authorizes native local exec.
238
247
239
248
```json
240
249
{
@@ -244,21 +253,25 @@ read, write, delete, list, grep, shell, or fetch on your machine **without** Cod
0 commit comments