Skip to content

Script Execution Service (SES)

Responsibility

Runs JavaScript (QuickJS), Python, or Bash for workflow steps. Exposed as capability script.execute.

Workflows use:

type: service_call
capability_name: script.execute
path: /v1/execute
runtime: javascript   # or python | bash
code: |
  result = input;

There is no first-class type: javascript|python|bash.

Capability

Capability Path
script.execute /v1/execute

Orchestrator resolves the provider via the capability registry, POSTs to /v1/execute (Bearer SES_SERVICE_TOKEN / ORCH_SES_TOKEN as configured), and unwraps {ok, result} as step output.

Architecture

Capability provider pattern:

  • Registers with capability-registry at startup
  • Orchestrator discovery via CAPABILITY_REGISTRY_URL
  • How-to with full contract: Script steps (flows)

Unified script contract

Every script sees:

Variable Description
input From payload_from
context Run context map (string values)
result Must be assigned — becomes step output

Deploy

  • Image / deployment: typically ses / script-execution-service
  • Service port: 8080 in cluster manifests

Health

  • GET /healthz
  • GET /readyz
  • GET /internal/capabilities