Skip to content

docs: browser execution tool design note - #351

Draft
neuromechanist wants to merge 1 commit into
developfrom
feature/browser-execution-tool-design
Draft

docs: browser execution tool design note#351
neuromechanist wants to merge 1 commit into
developfrom
feature/browser-execution-tool-design

Conversation

@neuromechanist

Copy link
Copy Markdown
Member

Design note for a community-agnostic, client-executed execute_code tool: code runs in the user's browser in a Pyodide worker owned by the widget, the agent loop stays in LangGraph on the server, and the two meet through tool_request / tool_result events with interrupt-and-resume. Lazy loading maps a uv-style workflow onto loadPackagesFromImports, micropip, and a per-community pinned lockfile. NEMAR is the first adopter; EEGLAB, HED, and BIDS adopt through configuration.

File: .context/browser-execution-tool-design.md

Companion decision on the NEMAR side: nemarOrg/nemar-cli ADR 0049 (PR linked in a comment below).

Draft for the owner's review. No code changes. The pr-review-toolkit pass was skipped because this PR is a design document; it will run before the PR leaves draft.

Client-executed execute_code tool: Pyodide in a widget worker, LangGraph interrupt/resume on the server, per-community runtime config with lockfile-pinned lazy loading. NEMAR is the first adopter; the design is community-agnostic.
@neuromechanist

Copy link
Copy Markdown
Member Author

Companion NEMAR decision: nemarOrg/nemar-cli#1292 (ADR 0049, supersedes ADR 0025).

@neuromechanist

Copy link
Copy Markdown
Member Author

First adopter's engine work: sccn/eegprep#324 (eegprep installable under Pyodide, ONNX ICLabel loaded through the runtime's JavaScript library hook).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant