fusedio/workbench

Use when a Fused canvas.toml contains (or needs) a [[comments]] block — e.g. the user asks to check/fix/resolve canvas comments, review feedback pins on a canvas, or leave comments on a canvas for someone else. Covers reading, writing, and resolving comments via the fused CLI pull/push workflow.

Format reference for canvas.toml files that define a Fused canvas (nodes, edges, viewport) plus the surrounding folder layout ({udfName}.py, .json, .md, .html, _shared.fused). Use when creating, editing, or validating any canvas.toml, adding/removing UDF nodes, wiring edges, defining folder groupings, or scaffolding a new canvas folder.

Ingest data into H3 hex datasets and query them with the fused.h3 API — partitioning points, geometries, gridded rasters (ERA5-style) or tables that already carry an H3 column into hex-sorted Parquet as server-side runs, registering them with fused.h3.index, and reading them back with fused.h3.query. Also covers the published ERA5 and GridMET hex datasets. Use when converting data to H3, building or appending to a hex dataset, following or retrying a partition/index run, querying one by point/bbox/cell/time, or reading ERA5/GridMET weather by location.

Reference for using Fused's built-in integration connections inside UDFs. Covers data sources (Snowflake, BigQuery, GCS, S3, Airtable, Notion, Google Drive), compute/inference providers (Modal, Hugging Face, Baseten, Daytona, ComfyOrg, Slack), and LLM providers (Anthropic, OpenAI) — the fused.api connect helpers, secrets access, and common operations (query, write, list, invoke, infer). Use when the user is writing a UDF that reads from, writes to, or calls out to a connected service.

Orientation to what Fused is and when to use it. Use when deciding whether to use Fused for a task, planning a new Fused project, or understanding Fused's capabilities as a remote Python execution platform.

What a Fused UDF can import and shell out to at run time — the Python packages and versions in the realtime and batch images, system binaries, DuckDB extensions, and how to get a package that isn't installed. Use before importing a library in a UDF, when a UDF fails with ModuleNotFoundError or a version-specific API error, or when choosing between libraries for a UDF.

Comprehensive guide for writing Fused User Defined Functions (UDFs). Use when helping users create, optimize, or debug UDFs, including function structure, parameter handling, performance optimization, agent-friendly design, and security best practices.

Reference for the legacy Fused Python SDK command line interface, now namespaced under fused workbench. Use when the user asks how to run, push, share, or otherwise manage UDFs, canvases, files, or secrets via the Fused workbench CLI, or when authoring shell commands that invoke fused workbench.

Authoring reference for Fused canvas HTML template nodes — the .html file in a canvas folder that renders as a sandboxed iframe with window.fused (fused.params, fused.runPython) and $param / {{udf}} substitution. Use when creating, editing, debugging, wiring, or sharing an HTML node, when a page needs to read canvas params or call a canvas UDF from JavaScript, or when deciding between an HTML node, the JSON-UI html widget, the iframe widget, and a Python UDF that returns HTML.

JSON schemas for Fused canvas UI widget components (text, text-input, button, dropdown, charts, maps, sql-table, form, transformer, etc.). Use when authoring or editing widget JSON files (e.g. widget_*.json in canvas directories), validating widget props, or answering questions about which fields a given widget type accepts.