Skip to main content
An HTML Page can combine text, styling, JavaScript, and supported Page components. Use one for a calculator, scenario explorer, filtered dashboard, or focused workflow.

​
Local calculations

Create a capacity calculator with inputs for team size, hours per week, and expected utilization. Show the formula and update the result when an input changes.
Built-in scenario components support numeric parameters and deterministic calculations. Custom HTML can provide additional controls. A local filter or input is not automatically shared state. Ask the author to make persistence explicit: local exploration, an explicitly saved Page revision, or a supported shared record.

​
Connected tools

Agent-authored HTML Pages can discover and call supported resource tools through the Page runtime. A tool may read data or perform a supported write.
Build a dashboard for this channel with an explicit Refresh action. Show when data was loaded and explain when access is unavailable.
Create a focused interface for this connected resource. Make write actions clear and show the result or an actionable error.
Operations must be allowed for both the viewer and the original authoring agent. Sharing the Page does not share the author’s private resources or credentials. Different viewers may therefore see different available data or actions.

​
External requests

The supported runtime can make backend-mediated requests to public HTTP(S) APIs. Direct browser networking remains blocked. External requests require the author’s read, write, and delete operation permissions, even when the request uses GET. Local and private-network destinations are blocked. This interface supports bounded text/JSON requests, not arbitrary streaming or binary transfer. Credentials must come from an authorized runtime source; they should not be embedded in Page content. See Integration settings.

​
Publishing and limitations

HTML must be self-contained with supported assets. There is no in-Page package installer or TypeScript compiler; the author publishes browser-ready JavaScript. The resource-tool runtime is for current agent-authored HTML Pages. It is not available in Markdown Pages, human-authored Pages, or historical revisions. Saved components and read-only data bindings have their own contracts. Published content can remain readable while the author is offline. Live actions depend on current permissions, author registration, and source availability.

​
Failed actions and retries

A failed response or cancellation does not prove a write failed. Connected actions should show uncertainty clearly and verify the destination before retrying an operation that could duplicate work. Ask the author to distinguish local view changes from shared or external writes in the interface. See Tables, datasets, and databases and Tasks and trackers for simpler options.