@cloudflare/computer

Minor Changes

• getWorkspace() now returns a lazy client immediately which resolves on the first call. useThink and the Think compatibility methods are removed; @cloudflare/think 0.21 and later take a Workspace as it is.

• WorkerJavaScriptBackend keeps its Durable Object alive while executions run, and adds a maxCpuMs option.

• just-bash is now an optional peer dependency and should be installed manually when using @cloudflare/computer/backends/worker-shell.

Patch Changes

• getWorkspace() accepts any Durable Object stub whose class has __getWorkspaceStub(), without a cast.

• WorkspaceProxy and WorkspaceServiceProxy wake their host Durable Object by name, so ctx.id.name survives a wake caused by a container or Dynamic Worker callback. WorkspaceRef, WorkspaceProxyProps and WorkspaceServiceProxyProps accept an optional name, filled in from ctx.id.name when the backend runs in the host object itself.

• deprecated

  Workspace, its filesystem, the worker-javascript backend, mounts, agent tools, Git, Assets, and Artifacts are now stable; LegacyContainerBackend is deprecated in favor of ContainerBackend; the container and worker-shell backends, ws:container, sync, and computerd stay experimental.

Patch Changes

• Add forAISDKTools() in @cloudflare/computer/tools/ai-sdk to serve an AI SDK tool set to isolate JavaScript as ws:tools; see ws:tools documentation.

• The edit tool bounds its diff with maxDiffLines and maxDiffBytes and reports diffTruncated; see edit tool documentation.

• Fix issue when creating a host module with no functions in the JavaScriptWorkerBackend; see host module documentation.

• The exec tool's input is an object rather than any JSON value; see exec tool documentation.

• The exec tool parses an input object sent as a string of JSON; see exec tool documentation.

• Tool sets take execOutput: { maxLines, maxBytes } for the exec tool's output limits; see tool option documentation.

• Host module factories receive the Workspace's assets client as host.assets; see host module documentation.

• WorkerJavaScriptBackend now lazily reads each host module's description; see module documentation.

• Mounts can now declare a version to support schema migrations; see mount version documentation.

• createPiTools results carry each tool's own output as details; see pi documentation.

• Add ws:tools to provide the JavaScript worker backend programmatic access to tools; see ws:tools documentation.

• The grep tool's include and exclude, and the find tool's exclude, take one glob or a list; see grep tool documentation.

• Add @cloudflare/computer/tools/core, which exports defineExec without an agent library; see tool documentation.

• Tool sets take root to confine the file tools to one directory; see root documentation.

• Add WorkerBundle, a read-only mount that copies files from the deployed bundle or an imported file tree; see mount documentation.

• Add @cloudflare/computer/vite with a computerBundle() plugin that bundles a directory into a Vite-built worker for WorkerBundle; see mount documentation.

• ws:artifacts adds createToken and share for minting git tokens and clone URLs; see ws:artifacts documentation.

• Add ws:assets so isolate JavaScript can publish a Workspace file to a time-limited URL; see ws:assets documentation.

• createContainerModule({ maxOutputLines }) limits each ws:container stream by lines as well as bytes; see ws:container documentation.

• createContainerModule({ prelude }) runs shell text such as set -o pipefail before each ws:container command; see ws:container documentation.

• ws:container now keeps the end of each stream for a Workspace with output: false; see ws:container documentation.

• ws:tools lists the tools code can import in its description; see ws:tools documentation.

Minor Changes

• createAITools moves to @cloudflare/computer/tools/ai-sdk; see tool wiring documentation.

• The exec option (now ExecBackendOptions) has been refactored to use runtime.backends(); see tool option documentation.

• The exec tool shows the last maxLines (2000) lines or maxBytes of each stream with a pointer to the full output on disk; see exec tool documentation.

• ws:git and ws:artifacts are no longer installed by default: add createGitModule() and createArtifactsModule(); see ws:git documentation.

• Remove WorkerJavaScriptBackend's maxConcurrentExecutions option, leaving the platform's own limit on concurrent Dynamic Workers; see execution limit documentation.

• Consolidate trustedModules with modules in WorkerJavaScriptBackend; see module documentation.

• runtime.exec results keep only the last 2000 lines or 64 KiB of each stream and save the full output to a Workspace file, configured with new Workspace({ output }) or turned off with output: false; see long output documentation.

• Fix an issue in JavaScriptWorkerBackend where a source module could import a Workspace file; see source module documentation.

Patch Changes

• JavaScriptWorkerBackend now supports absolute imports e.g. /workspace/lib/util.js; see import documentation.

• Improve WorkerShellBackend and ContainerBackend tool descriptions including egress information; see exec tool documentation.

• Add runtime.backends() to WorkspaceClient allowing tools to be created from workspace stubs; see tool wiring documentation.

• The exec tool now tells the model to put module code in an export default async function (input) shape.

• The exec tool only documents backend and input when needed; see exec tool documentation.

• A cyclic argument to a node:fs or host module call fails with a "must be acyclic" error; see execution limit documentation.

• Isolate JavaScript modules now need a default export, and fail before running without one.

• Isolate JavaScript code can now import Node.js built-ins such as node:path, node:crypto, and node:zlib.

• The JavaScript backend now creates its root directory (/workspace) if the Workspace doesn't have one.

• The JavaScriptWorkerBackend now strips non-serializable return values matching JSON.stringify(); see isolate JavaScript documentation.

• Isolate JavaScript runs now fail on I/O at module scope or an unhandled rejection, instead of completing silently, with no output.

• JavaScriptWorkerBackend now uses native RPC for modules bindings; see execution limit documentation.

• Imports of ws:* and other configured modules work when compatibilityFlags includes new_module_registry; see module documentation.

• Tools built from a remote getWorkspace() client of a Workspace without an assets publisher no longer offer a publish tool; see tool wiring documentation.

• Add workspace.runtime.backends(), which lists each backend's id, protocol, whether it is callable, and its description for a model, including the modules a WorkerJavaScriptBackend can import; see backend routing documentation.

• Each JavaScriptWorkerBackend now only stores each module once, so a large bundle counts once; see module documentation.

• A DO's ctx.storage can now be passed to a Workspace without casting.

• Workspace filesystem errors no longer repeat the path.

• Add ws:container so isolate JavaScript can run shell commands in the Workspace's ContainerBackend; see ws:container documentation.

• ws:git's cli accepts a leading -C <path> as its working directory; see ws:git documentation.

Minor Changes

• Rename the platform-scheduled container backend to LegacyContainerBackend; see container backend documentation.

• Add Workspace tool sets for pi (createPiTools from @cloudflare/computer/tools/pi-ai) and TanStack AI (createTanStackTools from @cloudflare/computer/tools/tanstack-ai); see the tool interface docs.

Patch Changes

• Keep configured paths local to the container instead of syncing them with the Durable Object using ContainerBackend.ignore; see local-only path documentation.

• Add ContainerBackend for durable-object-scheduled containers; see container backend documentation.

• Expand ws:git with full-history clones by default and additional cat-file, log, and command-specific help options; see Git interface documentation.

Patch Changes

• Document the symbolic-link filesystem surface under docs/04_filesystem_interface.md.

• Extend Workspace.fs to include rename(oldPath, newPath).

• find now accepts exclude e.g. ws.fs.find("/workspace", "**/*.ts", { exclude: ["node_modules/**"], }).

• Improve performance of git diff when given named paths.

Minor Changes

• The container's HTTP surface now requires a bearer token. The host generates a secret, passes it to the container as RPC_CLIENT_SECRET at launch, and sends it on /connect. Readiness at /health stays open, and leaving the variable unset disables the checks. Before opening a session the host checks that the container refuses an unauthenticated request and fails the connect if it does not, so a container or image predating this has to be recycled. The container's dial-back to the host carries the same secret, and the host refuses an upgrade that does not present it.

• The /connect caller now provides both API & healthcheck endpoints. The container no longer builds either path itself, so a host is free to serve them wherever it likes.

• IWorkspaceContainerAPI.start() and restart() now take a single ContainerLaunchSpec of { env, enableInternet } instead of two arguments, and return which of launched, adopted or relaunched happened. Each launch records its spec, and a container found already running is relaunched unless it matches, because neither the environment nor the internet flag can be changed on a live container. A container started outside this API has no record and is relaunched rather than trusted. setInactivityTimeout() joins the interface so a caller that pre-starts containers, such as a warm pool, does not need to reach past it.

• A command run through the shell no longer inherits the container's whole environment. It receives PATH, HOME, TMPDIR, TZ, LANG, TERM, the LC* family, and any variable prefixed COMPUTER_VAR*, which arrives with the prefix stripped so COMPUTER_VAR_NODE_ENV becomes NODE_ENV. A workspace that relied on some other inherited variable needs the prefix.

• The UPSTREAM_URL environment variable has been removed along with the container's own sync loop. Syncing is driven by whichever peer holds the other end of the Cap'n Web session.

• The Cap'n Web /ws endpoint has been renamed to /api at both ends of the connection. A durable object that routes the container's outbound upgrade must match /api in its own fetch handler. Support for the Cap'n Web HTTP batch transport has been removed, so /api carries a websocket only.

• Workspace.pull() and Workspace.push() are now async iterables that commit one block of changes per iteration. This allows a caller to implement a deferred post-exec sync across several invocations. See ./docs/02_sync_protocol.md for details.

• Make the artifacts session id optional: createArtifact(binding) now returns a client over the whole namespace rather than requiring a session to scope by. See ./docs/15_artifacts_interface.md for details.

Patch Changes

• Create missing parent directories while applying sync entries.

• Fix issue where the edit tool would rewrite the whole file when oldText doesn't match exactly.

• Sync node_modules by default so package manager installs persist across workspace runtimes.

Minor Changes

• Consolidate egress configuration across the existing backends. See ./examples/egress for details.

• Expose bounded workspace byte reads through RPC and return paginated directory listings with file metadata.

• Extend the read tool to support image and data formats.

• Updated find and grep tools to support additional filtering parameters, a delete tool.

• Reduced the size of bundles using worker-shell by making many commands opt-in. See the documentation for details.

Patch Changes

• Cut peak memory during a sync pull. Applying a file entry now links the chunks the sender already staged instead of reading them back and joining them into one whole-file buffer, which used to hold roughly twice the file size in the isolate at once.

• Fix git diff/status/log edge cases, batch sync hash probes within Durable Object SQLite limits, and count tracked RPC targets by identity.