Skip to content

Unify run-script surface with task-engine operator model (design first) #79

Description

@andywithcamera

ULow-priority, DESIGN-FIRST (owner aligned 2026-08-30). run-script-view.html is currently a standalone developer console (CodeMirror + run) with NO concept of: which agent identity it runs as, run history/audit, or a schedule/recurring seam. Compare with the task engine spec (#67-70, #72).

This is a strategic seam, not a visual bug - the run-script surface is the natural OPERATOR surface for the task/agent engine but is currently orphaned from it. Needs a design conversation before it becomes a build item:

  • Run as which identity/agent?
  • Run history + audit surfacing.
  • Recurring/scheduled runs.
    Do NOT build yet.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions