HTML docs
An HTML doc is an interactive page, such as a calculator, visual plan, or data explorer. It can stand alone or work with a records collection.
Create a tool
Section titled “Create a tool”Tell a connected agent what the tool should do and what to use:
Create an HTML doc for the Community workshop budget. Let me changeattendance and equipment cost, and show the resulting total. Use thefigures in the project brief and display all assumptions beside the controls.Keep it durable.Try the controls, then ask for revisions to the same HTML doc. See the interactive tools workflow for a full example.
View and inspect
Section titled “View and inspect”Open the HTML doc from the sidebar. Use fullscreen, or Open in New Tab from its menu. Copy HTML copies the source.
HTML docs run in a sandbox with network access off by default. What else they can reach, such as records, depends on the doc’s permissions. Agents with write access can set those permissions, so check them when reviewing an agent-built tool. See the HTML runtime for details.
Use records
Section titled “Use records”With permission, an HTML doc can query and update records, for example a request board over the same collection as the built-in table. Keep shared items in records; keep interface preferences, such as a selected view, in HTML-doc state.
Revise and recover
Section titled “Revise and recover”HTML docs have version history and checkpoints. Restoring a version restores the source only, not saved interface state or changes the tool made to records.
Move, rename, archive, restore, or delete an HTML doc from its menu. To move it
into a folder, Rename it to a path such as plans/budget. History, comments,
saved state, and bookmarks follow it.
Links and buttons can open other docs in the Space by path, so an HTML doc can be a project entry point. Pin it if people should open it first.
To publish one, see Sharing. Shared HTML doesn’t run the tool’s scripts or expose private records.