Documentation
¶
Overview ¶
Package scriptshow is show_scripts, the presentation-only tool that opens the portal's Automations pages for the human. It carries no script data and reads no store, which is why it is a package of its own rather than a corner of the script layer's tool surface (internal/platform/scriptlayer registers it beside manage_script).
Index ¶
Constants ¶
const ToolName = "show_scripts"
ToolName is the MCP tool name of the presentation-only trigger that opens the portal's script pages for the human.
Variables ¶
This section is empty.
Functions ¶
func Register ¶
Register registers show_scripts: a presentation-only tool whose only job is to point the human at their scripts, their schedules, and what those have been producing. portalURL is the deployment's public address, empty when it has not been told one.
It follows the show_prompts split (#1040) for the same reason that one exists. A UI is for the human, but it is opened in response to a tool call, and tool calls are made by the agent; a presentation surface attached to the tool an agent uses for its own work puts a page in front of the user every time the agent reads a script. So the two are separate tools: every script operation an agent performs — create, edit, validate, dry-run, read a run — lives on manage_script and renders nothing, and this tool does no data work an agent would ever call it for.
It is registered wherever scripts are kept, including a deployment that cannot execute them: what a script is and what it last did are worth seeing even where nothing will run one.
Types ¶
This section is empty.