GGitHubAdd celld example (#100)
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Add celld example (#100) `@cloudflare/computer` did not have an example showing how a Workspace and an Agents chat application run on celld. celld has no managed Workers AI binding, and its current Worker Loader cannot pass the Workspace filesystem capability into a loaded Worker, so existing Workers patterns do not run unchanged. This adds a prototype centered on one `CelldAgent` durable object. `AIChatAgent` and `withWorkspace` share the same SQLite storage, `routeAgentRequest` exposes the standard Agents WebSocket route, and `createAITools()` gives the model the Workspace tools. The local harness starts an S3-compatible store, deploys the Worker, and enables celld's experimental Worker Loader. An AI SDK terminal client and a noninteractive smoke client use the same chat transport. The model calls the Workers AI REST API with an account ID and API token. The callable `exec` backend runs complete JavaScript modules with structured input and output; its tool description shows the required default export. Filesystem work stays in the dedicated Workspace tools because the loaded Worker cannot access the Workspace mount. | 1 个月前 | |
Add celld example (#100) `@cloudflare/computer` did not have an example showing how a Workspace and an Agents chat application run on celld. celld has no managed Workers AI binding, and its current Worker Loader cannot pass the Workspace filesystem capability into a loaded Worker, so existing Workers patterns do not run unchanged. This adds a prototype centered on one `CelldAgent` durable object. `AIChatAgent` and `withWorkspace` share the same SQLite storage, `routeAgentRequest` exposes the standard Agents WebSocket route, and `createAITools()` gives the model the Workspace tools. The local harness starts an S3-compatible store, deploys the Worker, and enables celld's experimental Worker Loader. An AI SDK terminal client and a noninteractive smoke client use the same chat transport. The model calls the Workers AI REST API with an account ID and API token. The callable `exec` backend runs complete JavaScript modules with structured input and output; its tool description shows the required default export. Filesystem work stays in the dedicated Workspace tools because the loaded Worker cannot access the Workspace mount. | 1 个月前 |