Skip to content
ThinkWork ThinkWork

Runtime Configuration

Runtime configuration determines which model, guardrail, budget state, and sandbox settings the managed runtime uses for a turn. In the current Space architecture, operators do not normally choose a runtime per top-level managed agent. They configure:

Resolution order

Section titled “Resolution order”

For a managed turn, ThinkWork resolves runtime settings like this:

Space override
  -> tenant platform-agent default
  -> deployment/runtime fallback

If a Space leaves a field empty, it inherits the tenant agent value. This is the intended common case.

Tenant agent defaults

Section titled “Tenant agent defaults”

The tenant agent carries the broad defaults:

  • Model.
  • Monthly budget.
  • Sandbox.
  • System prompt and role.
  • Baseline workspace files.

Set these conservatively. They are the values every Space receives unless it explicitly overrides them.

Space overrides

Section titled “Space overrides”

A Space can override:

OverrideUse when
ModelThe Space needs a cheaper, faster, or stronger model than the tenant default
Guardrail idThe Space needs a stricter or specialized guardrail
Monthly budget centsThe Space needs a local spending cap
Budget pausedThe Space should stop accepting new paid work while other Spaces continue
SandboxThe Space needs different code-execution constraints

Space overrides apply to new turns in that Space. In-flight turns finish with the configuration they already loaded.

Managed runtime substrate

Section titled “Managed runtime substrate”

The managed runtime runs on Bedrock AgentCore inside your AWS account. Earlier versions of the docs described a visible multi-runtime selector on individual agents and templates. That selector is no longer the primary user-facing control for normal tenant operation.

For user-facing operations, think in terms of tenant-agent defaults plus Space overrides. Runtime substrate differences are deployment and migration concerns unless a specific screen exposes them.

Failure and fallback behavior

Section titled “Failure and fallback behavior”
  • Missing Space override: inherit the tenant agent value.
  • Missing tenant agent value: use the deployment/runtime fallback.
  • Unavailable model or guardrail: the turn fails with a configuration error rather than silently using an unrelated setting.
  • Budget paused: new work in that scope is blocked until the pause is cleared.
Section titled “Related pages”