Managing a Thing (Manage Entity Page)

This article describes the default plugin's Manage Thing page. A custom plugin's manage page may look different, but the building blocks and ideas carry over.

The Manage Thing page is the operational hub for a single entity. It's where you drive one piece of work through its pipeline, and what it shows adapts to the active workspace's current status.

Always available

Whatever the status, the page gives you:

• a workspace selector to switch between this Thing's workspaces (its parallel working versions);
• a Thing information box — title, section, current status, total cost so far, and description — with inline edit for the details;
• the workflow launcher, which auto-fetches the workflows available for the current status. It's a single button when one workflow applies, a dropdown when several do. It also carries a "Run as test webhook" checkbox: test runs are real executions — they can incur cost and mutate state — they simply dispatch through the engine's test webhook. The checkbox resets when you change the selected workflow;
• the workflow execution history for the workspace, with each run's name, status, and start/finish times, and a link into its full execution log (test runs are badged);
• a danger zone for deleting the Thing (a confirmed, plugin-owned soft delete);
• and a documentation box.

Status-dependent content

The middle of the page changes with the workspace's status — showing the generated text once a text-generation workflow has run, an editable input box when it's your turn to provide feedback, a read-only view of that input afterwards, and a media output box once a media-generation workflow has produced an asset. In short: the page surfaces exactly the outputs and actions that make sense for where the work currently stands, and hides the rest.

The result is a single screen from which you launch each stage, review what came back, contribute your own input where needed, and watch cost and history accumulate — for one Thing, one workspace at a time.