Skip to content

docs: why yoagent-rutis plugins are not available in a Worker #326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yuanhao merged 1 commit into from
Oct 16, 2026
Merged

docs: why yoagent-rutis plugins are not available in a Worker #326

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/concepts/extensions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,7 @@ The loop and the `Extension` contract build for every target yoagent supports, s
| Decision models: `ToolGate`, `InputGuard`, the advisor (`decision` feature) | yes | yes, over HTTP or the [`yoagent-workers`](https://github.com/yologdev/yoagent/tree/main/integrations/yoagent-workers) binding to Workers AI |
| Built-in tools: shell, files, search | yes | no: there is no operating system |
| MCP servers | stdio and HTTP | HTTP only |
| Plugins through [`yoagent-rutis`](https://github.com/yologdev/yoagent/tree/main/integrations/yoagent-rutis): TypeScript (Node or Bun), Python, Go, pi extensions, DSH plugins | yes | no: each plugin runtime is a process the host starts, and a Worker cannot start one |
| Plugins through [`yoagent-rutis`](https://github.com/yologdev/yoagent/tree/main/integrations/yoagent-rutis): TypeScript (Node or Bun), Python, Go, pi extensions, DSH plugins | yes | no: the crate does not build for `wasm32` (rutis's host needs Tokio's networking), so not even a runtime on another machine over `wss` (its `websocket` feature) can be reached from a Worker |

A VM is a local machine as far as yoagent is concerned: the same build and the same features; only who runs it differs.

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/wasm-workers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ build for wasm32.
| `AgentTool`s you write; HTTP MCP (`with_mcp_server_http`) | `FileBackend` for `SharedState` |
| `SharedState` (in memory, or your own `SharedStateBackend`), sub-agents | `SkillSet` loading (compiles, but finds no directories: there is no filesystem) |
| The `decision` feature | `PriceTable::fetch_cached` (its disk cache) |
| `Extension`s written in Rust (`Budget`, `ToolGate`, `InputGuard`, your own) | Plugins through `yoagent-rutis` (TypeScript, Python, Go, pi, DSH): each runtime is a process, and a Worker cannot start one |
| `Extension`s written in Rust (`Budget`, `ToolGate`, `InputGuard`, your own) | Plugins through `yoagent-rutis` (TypeScript, Python, Go, pi, DSH): the crate does not build for `wasm32`, remote runtimes over `wss` included |
| Compaction: `LlmCompaction` runs only its deterministic tiers and never summarises | reqwest's default features (rustls TLS, HTTP/2, system proxy settings, charset decoding); SOCKS proxies |
| | The `openapi` and `gasp` features (they need the filesystem and a full Tokio) |

Expand Down
Loading