Skip to Content
Platform
PlatformRuntime manifest

Runtime manifest

Runtime registration is manifest-driven: a canonical .introspection/<runtime-slug>.yaml file names the runtime group, points at the recipe, and declares its runtime configuration.

The manifest lives in the Git repository connected through your organization’s GitHub integration. Registering it creates the runtime group; see Operating runtimes for the bootstrap procedure and its production warning.

name: support-agent
description: Customer support agent
path: apps/support-agent
runtime:
  llm_mode: byok
  resources:
    requests:
      cpu: "1"
      memory: 2Gi
      storage: 10Gi
    limits:
      cpu: "2"
      memory: 4Gi

The filename is the slug

The filename stem is the stable runtime-group slug, so it must itself be a valid slug: lowercase letters, digits, and single hyphens, up to 63 characters. name is a separate display name and does not have to match it.

Manifest keys

KeyWhat it declares
nameDisplay name for the runtime group.
descriptionOptional description shown in the dashboard.
pathThe recipe directory within the repository.
includesAdditional paths to include alongside the recipe.
stricttrue turns manifest keys outside the schema into errors instead of warnings.
runtime.kindThe runtime kind.
runtime.llm_modemanaged or byok — see LLM providers.
runtime.configRuntime configuration keys carried on the runtime version.
runtime.resourcesCPU, memory, and storage sizing — see below.
runtime.githubThe workspace-repository grant — see GitHub.

runtime.github declares the repositories this runtime’s tasks may check out into the sandbox, and how much the token minted for them may do. GitHub is the canonical explanation of the grant.

Resource sizing: runtime.resources

Resource requests describe the capacity a task needs the environment to reserve: CPU for processing time and memory for the working set. CPU and memory limits bound how much a task may use when the target environment applies those limits. requests.storage sizes the task’s scratch volume; storage is request-only and is not a durable-artifact quota.

The platform parses these as portable resource quantities and resolves them against the target environment’s defaults, minimums, schedulability guards, and available capacity. The resolved values can therefore differ from the manifest. A CPU or memory limit cannot be lower than its resolved request. Size requests and limits from representative workload behavior and revise them when startup, capacity, or task behavior shows the workload needs a different allocation; do not assume the authored quantities were applied unchanged.

  • Runtimes: the concept the manifest registers — groups, lanes, and version pinning.
  • Operating runtimes: creating the first version and controlling lanes.
  • GitHub: the canonical runtime.github grant reference.
  • Recipes → Manifest: the recipe-side declarations (package.json, pi.runtime) the runtime satisfies.
Last updated on