Question 1

How do I fix "Cannot read properties of undefined (reading 'WorkspaceServiceProxy')" when running worker-shell exec in Cloudflare Computer?

Accepted Answer

This error has two possible setup causes. Fix both:

1. Add the required `enable_ctx_exports` compatibility flag to `wrangler.toml`:

```toml
compatibility_flags = ["nodejs_compat", "experimental", "enable_ctx_exports"]

If using `wrangler.json`:

```json
{
  "compatibility_flags": ["nodejs_compat", "experimental", "enable_ctx_exports"]
}
```

2. Re-export `WorkspaceServiceProxy` from your Worker entry point:

```js
export { WorkspaceServiceProxy } from "@cloudflare/computer";
```

Restart or redeploy Wrangler, then retry:

```bash
curl -X POST localhost:8787/exec \
  -H 'content-type: application/json' \
  -d '{"cmd":"echo hi"}'
```

Without `enable_ctx_exports`, `ctx.exports` is `undefined`; without the re-export, `WorkspaceServiceProxy` itself is missing. Both mistakes produce the same misleading error. This was observed with `@cloudflare/computer@0.2.0`, `wrangler@4.123.0`, and `workerd@1.20260811.1`.

Question 2

How to fix the @cloudflare/computer `edit` tool rewriting the whole file and stripping smart quotes, dashes, or trailing whitespace when `oldText` does not match exactly?

Accepted Answer

Root cause: when exact matching fails, `applyEditsToNormalizedContent` in `packages/computer/src/tools/fs/edit-diff.ts` matches against a fuzzy-normalized copy, but incorrectly uses that normalized copy as `baseContent` for both the write and diff. Therefore unrelated Unicode punctuation and trailing whitespace are flattened.

Immediate workaround: make `oldText` byte-for-byte exact. Remove accidental trailing spaces and preserve smart quotes (`U+201C`/`U+201D`), em dashes (`U+2014`), and the file's Unicode normalization. For the reproduction, change:

```ts
oldText: "let target = 1; "
```

to:

```ts
oldText: "let target = 1;"
```

Inspect invisible characters with `sed -n l path/to/file` or `od -c path/to/file`.

Permanent fix: keep the normalized content only for matching, maintain a source-offset map from normalized characters back to the original file, splice replacements into the original content, and generate the diff from original versus edited content. Reject ambiguous mappings, such as Unicode normalization merging characters or a match covering only part of an expanded ligature. This is implemented by the PR `fix: preserve files during fuzzy edits (#51)`.

Affected version: `@cloudflare/computer` `0.1.0-alpha.1` at commit `76d9e75`. Validate with:

```bash
npm test --workspace @cloudflare/computer -- src/tools/fs/repro.test.ts
```

Question 3

Why does the Worker JavaScript capability size error show a literal ${maxCapabilityBytes} instead of the configured byte limit?

Accepted Answer

The limit is interpolated in the size comparison, but the error message is generated as a plain double-quoted string, so `${maxCapabilityBytes}` is not replaced. Fix `capabilitiesModule()` in `packages/computer/src/backends/worker-javascript/module-graph.ts` by inserting the configured value when generating the module, for example: `throw new Error(${JSON.stringify(`Workspace capability request exceeds ${maxCapabilityBytes} bytes.`)});`. With `maxCapabilityBytes: 256`, the generated runtime code must become: `throw new Error("Workspace capability request exceeds 256 bytes.");`. Rebuild or regenerate the Worker module and redeploy. If available, update to a release containing PR #99 instead of patching manually.

Question 4

Why did the Cap'n Web WebSocket endpoint move from /ws to /api in computerd 0.3.0?

Accepted Answer

In computerd 0.3.0, the Cap'n Web endpoint was consolidated: use `/api` for WebSocket connections instead of `/ws`. The server distinguishes a WebSocket request from an HTTP request by the `GET` request with `Upgrade` headers. The old `/ws` path was removed. Note that HTTP batch support was also removed in 0.3.0 because it could not connect to streams returned from RPC calls after the streams migration.

Question 5

Why does Workspace.fs expose symlink(), readlink(), lstat(), and chmod() when the documentation says symbolic links are internal?

Accepted Answer

The documentation is outdated. In the shipped API, these methods are intentionally public on `WorkspaceFilesystem` and are mirrored across the Workers RPC boundary by `WorkspaceFilesystemStub`.

Use them as the Promise-based filesystem API:

```js
await workspace.fs.symlink(targetPath, linkPath);
const target = await workspace.fs.readlink(linkPath);
const linkStats = await workspace.fs.lstat(linkPath);
await workspace.fs.chmod(filePath, 0o644);
```

`stat()` follows a trailing symbolic link and reports the target, while `lstat()` reports the link itself. Relevant errors include `ENOENT` for a missing path, `EINVAL` for an invalid argument or operation, and `ELOOP` when too many symbolic links are encountered.

The fix is to update `docs/04_filesystem_interface.md` to document `symlink`, `readlink`, `lstat`, and `chmod`, and remove the claim that symbolic links are internal only. Removing these methods would be a breaking API change.

computer

Overview

README Preview

FAQ (5)

同类型项目

tensorflow

superpowers

everything-claude-code

flutter