Rhys SullivanVersion Packages (#2048)3890d6f1 month agoHistory
448 lines · 16.3 KB · MarkdownRawDownload

@executor-js/execution

1.6.10

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.6.10
    • @executor-js/codemode-core@1.6.10

1.6.9

Patch Changes

  • #1964 89b0f8d Thanks @dhairyashiil! - Completed MCP execute results now include toolName when a script successfully uses exactly one connected tool. Executions that use distinct tools remain unlabeled, and internal call provenance is not exposed in the MCP response.

  • #1976 40b2f2e Thanks @SunkenInTime! - Carry an approval's persistence choice through elicitation, so Codex Computer Use stops asking to use the same app on every call.

    Computer Use offers persist: ["session", "always"] in the prompt's terms and remembers the app only when the answer names one. Executor dropped the offer on the way in (the terms projection kept strings only) and the choice on the way out (every adapter rebuilt the reply from action and content), so each accept was one-time. ElicitationResponse now has meta.persist; the MCP plugin, the app-server bridge, and the MCP host pass it through; the model-mode resume tool and the browser approval page let the approver pick from the offered scopes. Nothing is chosen automatically: a bare accept still approves once.

  • #1942 3c263d7 Thanks @RhysSullivan! - Add a search and invoke MCP mode (?mode=passthrough, executor mcp --mode passthrough). Search returns bounded pages of matching tool IDs and input schemas. Invoke validates arguments and runs the selected tool, with native client approval and workspace blocks enforced. The MCP catalog stays at two tools regardless of integration count.

  • Updated dependencies [40b2f2e, 65d939e, 3c263d7, be77521, cc0fd8f, 85cf428, 38a7725, 3fd28a5, 929b233]:

    • @executor-js/sdk@1.6.9
    • @executor-js/codemode-core@1.6.9

1.6.8

Patch Changes

  • Updated dependencies [31a8042, b5271a6, caa0391]:
    • @executor-js/sdk@1.6.8
    • @executor-js/codemode-core@1.6.8

1.6.7

Patch Changes

  • Updated dependencies [98d6c6a]:
    • @executor-js/sdk@1.6.7
    • @executor-js/codemode-core@1.6.7

1.6.6

Patch Changes

  • #1866 21119da Thanks @RhysSullivan! - Large execute results are measured once, not once per span

    The result-size telemetry probe serializes the whole returned value to count its characters, and that cost grows with the payload. The same result object was walked again every time it was stamped onto another span: an operator-approved run measured it twice (inner and outer span), and every retried resume that replayed a settled outcome measured it again. The measurement is now computed once per result object and reused, so a large result pays one size walk no matter how many spans report it. Response text, structured content, and span attribute values are unchanged.

  • Updated dependencies []:

    • @executor-js/sdk@1.6.6
    • @executor-js/codemode-core@1.6.6

1.6.5

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.6.5
    • @executor-js/codemode-core@1.6.5

1.6.4

Patch Changes

1.6.3

Patch Changes

  • Updated dependencies [c1f51b7, 02b52cd]:
    • @executor-js/sdk@1.6.3
    • @executor-js/codemode-core@1.6.3

1.6.2

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.6.2
    • @executor-js/codemode-core@1.6.2

1.6.1

Patch Changes

  • #1741 62748e8 Thanks @RhysSullivan! - Opt-in per-integration search tools on the MCP surface

    Connecting with ?search_tools=true (stdio: executor mcp --search-tools) adds one minimally-described search_<integration> MCP tool per connected integration, so the integration namespaces reach the model as tool names it can see without calling anything. Each call routes through the same flow as tools.search({ namespace }) inside execute, and the tool list comes from the same inventory the execute description shows. Off by default; a clean endpoint URL is unchanged.

  • #1749 d4afe0c Thanks @RhysSullivan! - Slim the per-integration search_<integration> tool definitions to under half their size: one shared one-line description (the tool name already carries the namespace) and a single bare query parameter, dropping the limit/offset knobs. A session pays for these definitions once per connected integration, so the surface now costs ~2k tokens instead of ~5k at 30 integrations; paging through a namespace belongs in execute.

  • Updated dependencies [55180cb]:

    • @executor-js/sdk@1.6.1
    • @executor-js/codemode-core@1.6.1

1.6.0

Patch Changes

  • Updated dependencies [a2d1417]:
    • @executor-js/sdk@1.6.0
    • @executor-js/codemode-core@1.6.0

1.5.42

Patch Changes

  • Updated dependencies [d3f0617]:
    • @executor-js/sdk@1.5.42
    • @executor-js/codemode-core@1.5.42

1.5.41

Patch Changes

  • Updated dependencies [d572658]:
    • @executor-js/sdk@1.5.41
    • @executor-js/codemode-core@1.5.41

1.5.40

Patch Changes

  • Updated dependencies [8ba64f6]:
    • @executor-js/sdk@1.5.40
    • @executor-js/codemode-core@1.5.40

1.5.39

Patch Changes

  • Updated dependencies [6c316c7]:
    • @executor-js/sdk@1.5.39
    • @executor-js/codemode-core@1.5.39

1.5.38

Patch Changes

  • Updated dependencies [6a924dd]:
    • @executor-js/sdk@1.5.38
    • @executor-js/codemode-core@1.5.38

1.5.37

Patch Changes

  • Updated dependencies [657b913]:
    • @executor-js/sdk@1.5.37
    • @executor-js/codemode-core@1.5.37

1.5.36

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.36
    • @executor-js/codemode-core@1.5.36

1.5.35

Patch Changes

  • Updated dependencies [1b9b1f1]:
    • @executor-js/sdk@1.5.35
    • @executor-js/codemode-core@1.5.35

1.5.34

Patch Changes

  • #1422 e2712db Thanks @RhysSullivan! - A token refresh the authorization server definitively rejects (any RFC 6749 error code, not just invalid_grant) now surfaces to the sandbox as an oauth_refresh_failed auth failure carrying the server's error code and description, instead of being scrubbed to "Internal tool error". invalid_grant still classifies as oauth_reauth_required. Code-less failures (transport blips) keep retrying as before.

  • Updated dependencies [e2712db, 7207347, 0c4e9b4]:

    • @executor-js/sdk@1.5.34
    • @executor-js/codemode-core@1.5.34

1.5.33

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.33
    • @executor-js/codemode-core@1.5.33

1.5.32

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.32
    • @executor-js/codemode-core@1.5.32

1.5.31

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.31
    • @executor-js/codemode-core@1.5.31

1.5.30

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.30
    • @executor-js/codemode-core@1.5.30

1.5.29

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.29
    • @executor-js/codemode-core@1.5.29

1.5.28

Patch Changes

  • Updated dependencies [1c48182]:
    • @executor-js/sdk@1.5.28
    • @executor-js/codemode-core@1.5.28

1.5.27

Patch Changes

  • Add a skills tool and slim the always-loaded execute description. The execute tool's calling-convention guide now lives behind skills({ name: "execute" }), so a session loads it on demand instead of carrying it up front. The execute description keeps a one-line intro, a pointer to the skill, and a names-only list of the integrations the user has connected (deduped across connections, no per-connection prefixes).

  • Updated dependencies []:

    • @executor-js/sdk@1.5.27
    • @executor-js/codemode-core@1.5.27

1.5.26

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.26
    • @executor-js/codemode-core@1.5.26

1.5.25

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.25
    • @executor-js/codemode-core@1.5.25

1.5.24

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.24
    • @executor-js/codemode-core@1.5.24

1.5.23

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.23
    • @executor-js/codemode-core@1.5.23

1.5.22

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.22
    • @executor-js/codemode-core@1.5.22

1.5.21

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.21
    • @executor-js/codemode-core@1.5.21

1.5.20

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.20
    • @executor-js/codemode-core@1.5.20

1.5.19

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.19
    • @executor-js/codemode-core@1.5.19

1.5.18

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.18
    • @executor-js/codemode-core@1.5.18

1.5.17

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.17
    • @executor-js/codemode-core@1.5.17

1.5.16

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.16
    • @executor-js/codemode-core@1.5.16

1.5.15

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.15
    • @executor-js/codemode-core@1.5.15

1.5.14

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.14
    • @executor-js/codemode-core@1.5.14

1.5.13

Patch Changes

  • #976 8244fee Thanks @RhysSullivan! - Make paused-execution resume reliable: resume is now idempotent (a retried resume replays the recorded outcome instead of failing with "No paused execution"), execution ids are globally unique so a rebuilt engine can never re-mint an id a stale client still holds, pauses abandoned by a dead sandbox are dropped and their terminal outcome kept for late resumes, and an expired or lost pause now returns recovery guidance (re-run execute) instead of a bare miss.
  • Updated dependencies []:
    • @executor-js/sdk@1.5.13
    • @executor-js/codemode-core@1.5.13

1.5.12

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.12
    • @executor-js/codemode-core@1.5.12

1.5.11

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.11
    • @executor-js/codemode-core@1.5.11

1.5.10

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.10
    • @executor-js/codemode-core@1.5.10

1.5.9

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.9
    • @executor-js/codemode-core@1.5.9

1.5.8

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.8
    • @executor-js/codemode-core@1.5.8

1.5.7

Patch Changes

  • Updated dependencies [7cee242, 7cee242]:
    • @executor-js/sdk@1.5.7
    • @executor-js/codemode-core@1.5.7

1.5.4

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.4
    • @executor-js/codemode-core@1.5.4

1.5.3

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.3
    • @executor-js/codemode-core@1.5.3

1.5.2

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.2
    • @executor-js/codemode-core@1.5.2

1.5.1

Patch Changes

  • Updated dependencies []:
    • @executor-js/sdk@1.5.1
    • @executor-js/codemode-core@1.5.1

1.5.0

Patch Changes

  • #922 1ba0193 Thanks @RhysSullivan! - Move effect from dependencies to peerDependencies in the published library packages so consumers provide a single shared Effect instance.

  • Updated dependencies [7d7fbbd, 1ba0193]:

    • @executor-js/sdk@1.5.0
    • @executor-js/codemode-core@1.5.0