Buyer Guides
Cloudflare’s Think Workspace Change Leaves a Data-Mapping Decision
Cloudflare’s October 20 Think change separates retained files from usable workspace data. Compare project mappings, application reads and original file times.
On October 20, 2026, Cloudflare announced that Think and Agent Skills now use @cloudflare/computer for their workspace and filesystem tools. It deprecated @cloudflare/shell and Think’s createExecuteTool, ending their development and support that day. The announcement calls the workspace change breaking: files are not migrated automatically, and the new workspace can start empty while the old workspace records remain in their original tables. [1]
For an application buyer, the deliverable now needs a data mapping: which old file populations become available to the new workspace, what their names mean there, and which history remains usable. An accurate inventory of retained sources is a valuable starting point. It cannot establish that the application reads the required contents.
The target has a different workspace boundary
The maintainer migration guide, read on its main branch on October 21, describes one Computer workspace per Durable Object storage and no equivalent yet to Shell’s namespace option. It assigns each old namespace its own cf_workspace_<namespace> table; pre-switch Think used default. The old and new table families can coexist. For R2-backed old files, the rows hold metadata while the bytes reside in the bucket. This comparison concerns that Durable Object path; the guide lists no replacement for D1, custom SqlBackend or InMemoryFs usage. [2]
Think’s tools documentation, updated October 20, places its workspace files under the absolute working root /workspace. Built-in file tools arrive on each turn; execution needs a separately configured backend. [3] Having files available and having a configured way to execute code are distinct capabilities. Neither alone establishes which file a particular application task consumed.
TW20 starts with two retained populations
Consider fictional application TW20. Its ordinary Think files belong to the old default namespace. Its owner has also used a separate Shell workspace named projectB. Each contains /notes.md, with different contents: default holds the main project’s notes and projectB holds another project’s notes. The buyer requires both populations to remain readable, each project selection to retain its meaning, and each file’s original modification time to remain available through the target’s native file metadata. These are invented requirements and observations, with no migration or product test performed.
At the first stipulated observation, both source populations and their contents remain retained, while the new workspace opens empty. That is consistent with the announced transition. The retained sources answer where the material still exists. The empty target answers what is available through that new workspace at this observation. Together, they establish neither loss of the original contents nor a completed transfer.
The first proposal adds a complete source inventory and shows the default file at /workspace/notes.md. The guide illustrates that target path for an old /notes.md. [2] TW20 can now identify the default target content, but the proposal still leaves projectB’s destination unspecified. Two identical filenames in separate old namespaces do not prove that an overwrite occurred. The missing decision is how both populations will be represented and selected.
Give each target path an application meaning
A second fictional proposal explicitly maps default’s notes to /workspace/imported/default/notes.md and projectB’s notes to /workspace/imported/projectB/notes.md. These paths illustrate proposed application meaning; they are not a documented Cloudflare namespace replacement. The provider must establish that the representation is supported for the offered version and explain how the application’s project selection reaches the corresponding content.
Now stipulate those support and application relationships have been established: both files are visible with their intended contents, and the main-project task consumes the first while the projectB task consumes the second. Under these premises, the second proposal satisfies TW20’s content availability, separate project meaning and application-use requirements. A screenshot showing two files would establish less, because it would omit the task-to-file relationship.
The distinction also defines the remaining compatibility question. TW20’s stated requirement concerns selecting the right project content. A buyer requiring the old namespace API itself needs evidence for that additional requirement; two directory names cannot supply it. Nor does their presence establish an access-control boundary. The proposed mapping should carry only the meaning the application and offered support actually establish.
Original time is a separate part of the purchase
The migration guide says its supplied copy does not retain created_at or modified_at: Computer stamps copy time. It also does not retain per-file mime_type. [2] For TW20, even the second proposal’s stipulated successful content mapping therefore leaves the original-modification-time requirement unresolved if it relies only on that copy.
Suppose the main notes were last modified on October 16 and projectB’s notes on October 18, while both are copied on October 21. Those dates are fictional. Two October 21 target timestamps would describe the later copying event; they would not preserve the two original modification values. Correct contents at correct destinations cannot supply the missing history.
A supplementary history record could answer a revised requirement if it retains each original value and its relationship to the old namespace, old path and identified target file, and the application can use that record. That is an additional proposed deliverable requiring its own support. It becomes sufficient only if the buyer explicitly accepts history in that form. If the requirement is preservation in the target filesystem’s native modification field, a separate record leaves it unmet.
Choose the scope that reaches the required result
In TW20, the first proposal identifies one target file while retaining both sources. It leaves projectB’s target and the application relationships unresolved. The second proposal satisfies the requirements for both files, project selection and application use under the stated premises. Native preservation of original modification times remains unestablished.
Supported history records the application can read become a candidate answer only after the buyer explicitly revises the requirement for native modification times. If it remains mandatory, the offer still needs a supported way to meet it. The purchase comparison now has a defined boundary for each promised result.
The file-path and open-reader guide examines a different selection problem: an existing reader can retain a file after its current name changes. Here the relationship crosses workspace formats and application mappings. Keep those mechanisms separate when deciding which evidence a supplier’s file report provides.
For a broader application change, the model-registry and serving-release guide follows selected artifacts into the complete serving combination. This October 20 workspace announcement settles a narrower question: a package transition does not, by itself, establish that every required population, project meaning and historical value reached the application.
01Footnotes
Footnotes
- Cloudflare changelog, October 20, 2026; read October 21. Dated package transition, deprecation and retained-source/empty-target scope.
- Cloudflare Agents maintainer migration guide, main branch observed October 21, 2026. Workspace topology, path mapping and omitted metadata; not an immutable release reference.
- Cloudflare Think tools, updated October 20, 2026; read October 21. Workspace root, built-in file tools and separately configured execution.
Contact
Discuss Your Infrastructure Project
Tell us about your project, and our team will follow up to discuss the scope, requirements and availability.