## Summary
Instead of always adding inner function call outputs to the model
context, let js code decide which ones to return.
- Stop auto-hoisting nested tool outputs from `codex.tool(...)` into the
outer `js_repl` function output.
- Keep `codex.tool(...)` return values unchanged as structured JS
objects.
- Add `codex.emitImage(...)` as the explicit path for attaching an image
to the outer `js_repl` function output.
- Support emitting from a direct image URL, a single `input_image` item,
an explicit `{ bytes, mimeType }` object, or a raw tool response object
containing exactly one image.
- Preserve existing `view_image` original-resolution behavior when JS
emits the raw `view_image` tool result.
- Suppress the special `ViewImageToolCall` event for `js_repl`-sourced
`view_image` calls so nested inspection stays side-effect free until JS
explicitly emits.
- Update the `js_repl` docs and generated project instructions with both
recommended patterns:
- `await codex.emitImage(codex.tool("view_image", { path }))`
- `await codex.emitImage({ bytes: await page.screenshot({ type: "jpeg",
quality: 85 }), mimeType: "image/jpeg" })`
#### [git stack](https://github.com/magus/git-stack-cli)
- ✅ `1` https://github.com/openai/codex/pull/13050
- 👉 `2` https://github.com/openai/codex/pull/13331
- ⏳ `3` https://github.com/openai/codex/pull/13049
5.0 KiB
JavaScript REPL (js_repl)
js_repl runs JavaScript in a persistent Node-backed kernel with top-level await.
Feature gate
js_repl is disabled by default and only appears when:
[features]
js_repl = true
js_repl_tools_only can be enabled to force direct model tool calls through js_repl:
[features]
js_repl = true
js_repl_tools_only = true
When enabled, direct model tool calls are restricted to js_repl and js_repl_reset; other tools remain available via await codex.tool(...) inside js_repl.
Node runtime
js_repl requires a Node version that meets or exceeds codex-rs/node-version.txt.
Runtime resolution order:
CODEX_JS_REPL_NODE_PATHenvironment variablejs_repl_node_pathin config/profilenodediscovered onPATH
You can configure an explicit runtime path:
js_repl_node_path = "/absolute/path/to/node"
Module resolution
js_repl resolves bare specifiers (for example await import("pkg")) using an ordered
search path. Path-style specifiers (./, ../, absolute paths, file: URLs) are rejected.
Module resolution proceeds in the following order:
CODEX_JS_REPL_NODE_MODULE_DIRS(PATH-delimited list)js_repl_node_module_dirsin config/profile (array of absolute paths)- Thread working directory (cwd, always included as the last fallback)
For CODEX_JS_REPL_NODE_MODULE_DIRS and js_repl_node_module_dirs, module resolution is attempted in the order provided with earlier entries taking precedence.
Usage
js_replis a freeform tool: send raw JavaScript source text.- Optional first-line pragma:
// codex-js-repl: timeout_ms=15000
- Top-level bindings persist across calls.
- Top-level static import declarations (for example
import x from "pkg") are currently unsupported; use dynamic imports withawait import("pkg"). - Use
js_repl_resetto clear the kernel state.
Helper APIs inside the kernel
js_repl exposes these globals:
codex.tmpDir: per-session scratch directory path.codex.tool(name, args?): executes a normal Codex tool call from insidejs_repl(including shell tools likeshell/shell_commandwhen available).codex.emitImage(imageLike): explicitly adds exactly one image to the outerjs_replfunction output.- Each
codex.tool(...)call emits a bounded summary atinfolevel from thecodex_core::tools::js_repllogger. Attracelevel, the same path also logs the exact raw response object or error string seen by JavaScript. - Nested
codex.tool(...)outputs stay inside JavaScript unless you emit them explicitly. codex.emitImage(...)accepts a direct image URL, a singleinput_imageitem, an object like{ bytes, mimeType }, or a raw tool response object that contains exactly one image and no text.codex.emitImage(...)rejects mixed text-and-image content.- Example of sharing an in-memory Playwright screenshot:
await codex.emitImage({ bytes: await page.screenshot({ type: "jpeg", quality: 85 }), mimeType: "image/jpeg" }). - Example of sharing a local image tool result:
await codex.emitImage(codex.tool("view_image", { path: "/absolute/path" })).
Avoid writing directly to process.stdout / process.stderr / process.stdin; the kernel uses a JSON-line transport over stdio.
Debug logging
Nested codex.tool(...) diagnostics are emitted through normal tracing output instead of rollout history.
infolevel logs a bounded summary.tracelevel also logs the exact serialized response object or error string seen by JavaScript.
For codex app-server, these logs are written to the server process stderr.
Examples:
RUST_LOG=codex_core::tools::js_repl=info \
LOG_FORMAT=json \
codex app-server \
2> /tmp/codex-app-server.log
RUST_LOG=codex_core::tools::js_repl=trace \
LOG_FORMAT=json \
codex app-server \
2> /tmp/codex-app-server.log
In both cases, inspect /tmp/codex-app-server.log or whatever sink captures the process stderr.
Vendored parser asset (meriyah.umd.min.js)
The kernel embeds a vendored Meriyah bundle at:
codex-rs/core/src/tools/js_repl/meriyah.umd.min.js
Current source is meriyah@7.0.0 from npm (dist/meriyah.umd.min.js).
Licensing is tracked in:
third_party/meriyah/LICENSENOTICE
How this file was sourced
From a clean temp directory:
tmp="$(mktemp -d)"
cd "$tmp"
npm pack meriyah@7.0.0
tar -xzf meriyah-7.0.0.tgz
cp package/dist/meriyah.umd.min.js /path/to/repo/codex-rs/core/src/tools/js_repl/meriyah.umd.min.js
cp package/LICENSE.md /path/to/repo/third_party/meriyah/LICENSE
How to update to a newer version
- Replace
7.0.0in the commands above with the target version. - Copy the new
dist/meriyah.umd.min.jsintocodex-rs/core/src/tools/js_repl/meriyah.umd.min.js. - Copy the package license into
third_party/meriyah/LICENSE. - Update the version string in the header comment at the top of
meriyah.umd.min.js. - Update
NOTICEif the upstream copyright notice changed. - Run the relevant
js_repltests.