Repository navigation
docs: why yoagent-rutis plugins are not available in a Worker - #326
Merged
Merged
Conversation
Not because a Worker cannot start a plugin process — yoagent-rutis can reach remote runtimes over wss (its websocket feature) without starting one — but because the crate does not build for wasm32 (rutis's host needs Tokio's networking: mio refuses the target), remote runtimes included. Found by the fact-check of #325. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T7iq5hpndSiHQcnAsywKuG
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #325, from its fact-check, which finished after the merge.
What was wrong: #325 gave the reason "each plugin runtime is a process the host starts, and a Worker cannot start one". That isn't the whole truth. yoagent-rutis can reach runtimes on other machines over
wss(itswebsocketfeature) without starting any process.The actual reason: the crate does not build for
wasm32at all.cargo check --target wasm32-unknown-unknownfails inmio, with and without--features websocket, because rutis's host needs Tokio's networking. So remote runtimes can't be reached from a Worker either. The "no" stands; only the reason changes, in both places:docs/concepts/extensions.md, "Where extensions run";docs/guides/wasm-workers.md, "What is available".🤖 Generated with Claude Code
https://claude.ai/code/session_01T7iq5hpndSiHQcnAsywKuG