Skip to content

v1.6.4

Choose a tag to compare

View all tags
@github-actions github-actions released this 30 Aug 00:37
· 25 commits to main since this release
v1.6.4
5c0fa88
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch Changes

  • #1858 ffcfbc0 Thanks @RhysSullivan! - Add locally installed OpenAI Codex plugins as one-click integrations: Messages
    (iMessage/SMS), Chrome, Computer Use, Computer History, and OpenAI Developer
    Docs. They appear in the connect dialog with their own icons, and a card that
    cannot run yet says what to install and links to it.

    Tool calls reach the plugins through codex app-server rather than a plugin's
    own MCP server, because their services only honour calls from a Codex host
    session. Computer Use and Chrome ship no MCP server at all, so their APIs are
    projected as typed tools — list_apps, click, read_page, navigate — that
    compile to a single call each. No model turn is involved; nothing is bundled or
    downloaded, and a machine without Codex simply sees the setup steps.

    A plugin's own approval prompt now reaches the caller, and states the terms it
    carries: a browser prompt that persists for a site says so. Approvals are asked
    once per session rather than per call.

    Elicitation requests can carry implementation-defined metadata through
    FormElicitation / UrlElicitation, and a paused execution reports it. Both
    fields are optional and additive.

  • #1477 c0c7a0d Thanks @RhysSullivan! - Stop exporting credential-bearing URLs in telemetry. Every query parameter
    value, URL fragment, and userinfo component is stripped from exported span
    URLs — no parameter name is trusted — on every exporter path: the cloud span
    processors, the self-host OTLP exporter, the browser client's OTLP exporter,
    and the forwarded browser trace batches. User-supplied MCP endpoints are
    sanitized before being stamped onto spans.

  • #1841 d13151a Thanks @RhysSullivan! - 1Password: multiple named accounts. The provider now holds any number of named accounts — a work account next to a personal one, or a service-account token next to desktop-app biometrics — each scoping its own set of vaults. The settings card lists every account with independent edit and disconnect, existing single-account configs upgrade in place, and op:// refs keep their vault-first addressing: a vault name that exists in more than one account is an explicit ambiguity error, never a silent pick.

  • Updated dependencies [ffcfbc0, 10e16a5, 515d6aa, 06bf742]:

    • @executor-js/sdk@1.6.4
    • @executor-js/local@1.6.4
    • @executor-js/api@1.4.67
    • @executor-js/runtime-quickjs@1.6.4
Assets 24
Loading