Cloudflare drops @cloudflare/shell, breaking existing agent workspaces
Think and Agent Skills now run on a @cloudflare/computer workspace instead. There is no automatic migration, so agents built on the old shell package start with an empty workspace unless you copy the files yourself.
Cloudflare’s Think and Agent Skills tools now run on a workspace from @cloudflare/computer instead of @cloudflare/shell, according to a changelog post published on 20 October. Both @cloudflare/shell and Think’s createExecuteTool are deprecated as of today and will get no further development or support.
The two workspace formats store files in different tables, and Cloudflare is explicit that there is no automatic migration between them. An agent built against the old shell workspace will start with an empty workspace on the new one unless its files are copied across first. Cloudflare has published a script for exactly that in its “Migrating from @cloudflare/shell to @cloudflare/computer” guide. The move also lets you configure a JavaScriptWorkerBackend for the workspace, giving Think a JS execution environment alongside the existing filesystem tools.
const workspace = new Workspace({
backend: new WorkerJavaScriptBackend(env),
});Why it matters: if you’ve built an agent on Cloudflare’s Think or Agent Skills with a persistent workspace, upgrading without running the migration script first silently wipes out whatever that agent had stored, logins, generated files, scratch state. Anyone running this in production needs to run the migration before touching the dependency bump.
The caveat: this only affects Cloudflare Agents SDK users on Think or Agent Skills with @cloudflare/shell; everyone else can ignore it.