| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
examples, docs: repoint artifacts and prose at the renamed worker example The artifacts example clones this repo and copies EXAMPLE_PATH into the workspace at runtime; it still pointed at examples/worker, which the rename moved to examples/worker-shell, so the copy would fail once the rename landed. Update EXAMPLE_PATH and the surrounding prose, the root README link, AGENTS.md, and the artifacts example's own README, package.json, and wrangler.jsonc. | 1 个月前 | |
Rename @cloudflare/workspace to @cloudflare/computer (#20) | 1 个月前 | |
Version Packages | 23 天前 | |
docs, computer, computerd: say wrapper instead of facade "Facade" is a design-pattern name standing in for a plain word. Every prose use across the documentation, the package readmes, and the source comments becomes "wrapper", along with the one local variable in the computerd command-line tests that carried the term in its name. Three sentences needed more than the word swap to keep reading well: an observability comment that would have wrapped a span in a wrapper, a workspace comment whose wrappers wrapped their own entry points, and a project-layout line that listed the root export among the public entrypoints. | 21 天前 | |
Version Packages | 23 天前 | |
examples: Route the capnweb upgrade on /api The daemon and the host both serve the capnweb session on /api now, so the durable objects that route the container's outbound upgrade follow. Each example matched /ws in its fetch handler; the container example forwards every request to the backend and needed no change beyond its comments. | 21 天前 | |
examples/rlm: Add a structured RLM example (#122) * examples/rlm: Add a structured RLM example Show how Computer Workspaces, generated JavaScript, and a bounded trusted model module can implement map/reduce over long context. Compare direct context, JavaScript-only execution, and Structured RLM on official Oolong tasks with observable scoring and usage. * examples/rlm: Show rejected executor output Keep successful JavaScript executions visible when their returned shape cannot be scored. Sanitize invalid output into a metadata-only summary and explain the semantic capability mismatch in the comparison UI. | 5 天前 | |
examples/think-compare-runtimes: Warm-start containers through the workspace API The pool started containers with ctx.container.start() and an environment it built itself, which skipped everything the workspace API adds. The shared secret never reached the container, so its HTTP surface stayed unauthenticated while the host sent a bearer token it ignored, and the hardcoded internet flag became whatever the adopting workspace inherited. Warm starts now go through the API, so the launch carries the secret and is recorded for the adoption check. The environment and the internet flag travel together as a ContainerLaunchSpec, which is also what the adopting workspace compares against. The retry loop calls start() unconditionally now. It adopts a container already running with the same spec, so there is nothing left for the caller to decide from a `running` flag. A pool still cannot know the egress policy of the workspace that will adopt a container, so enableInternet has to agree with it by configuration. Disagreeing now costs a relaunch on adoption rather than the policy. ContainerLaunchSpec and ContainerRuntimeInfo are exported from the container entry point, since a consumer that pre-starts containers needs both. | 21 天前 | |
examples: Route the capnweb upgrade on /api The daemon and the host both serve the capnweb session on /api now, so the durable objects that route the container's outbound upgrade follow. Each example matched /ws in its fetch handler; the container example forwards every request to the backend and needed no change beyond its comments. | 21 天前 | |
docs: Describe the single /api endpoint Bring the written surface in line with the daemon. It serves one endpoint, /api, carrying one transport, and the HTTP batch alternative is gone: every call that returns data returns a ReadableStream, and delivering one needs a call from server to client that a batch session cannot complete. UPSTREAM_URL is removed from the environment tables and from the prose that described a daemon-driven sync loop. The lifecycle document claimed the Cloudflare backend wired that variable automatically, which was never true; the carrier is POST /connect and the durable object drives sync across it. That sentence is the one a reader lands on when working out how a container recovers after a restart, so it pointed at the wrong mechanism. The /connect description now shows the request naming a base and both paths, records the readiness probe reading base plus health, and covers the new watermarks endpoint and the handshake statuses. | 21 天前 | |
docs: align the docs with the unified execution backend Update the prose and interface listings for the execution changes: the shell wire field is source rather than command and carries an optional structured input; the exit event carries an optional structured result; the workspace no longer takes a waitUntil hook and a JavaScript run stays alive while its event stream is consumed; and the host command driver is the CommandExecutor, with encoding and result accumulation living in the runtime. Touches the capnweb wire contract, the runtime lifecycle and worker backend notes, the isolate JavaScript guide, the runtime migration table, and the computer and example READMEs. | 1 个月前 | |
examples/worker, docs: opt shell commands in by import Update the worker example and the worker-backend docs to the import-based command selection. The example imports the curl and sqlite groups and passes them to WorkerBackend's commands option, demonstrating that opting a command in is a single import and opting out is deleting it. The package README, the example README, and docs/12_worker_backend.md describe the always-on core, the per-command groups published at @cloudflare/computer/shell/*, the commands option, and the assembleShellModules helper for callers that build the Loader callback by hand. | 1 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 个月前 | ||
| 1 个月前 | ||
| 23 天前 | ||
| 21 天前 | ||
| 23 天前 | ||
| 21 天前 | ||
| 5 天前 | ||
| 21 天前 | ||
| 21 天前 | ||
| 21 天前 | ||
| 1 个月前 | ||
| 1 个月前 |