Runtime limits

import { createAdmin } from "@nylorun/admin";

const admin = createAdmin();

const { limits } = await admin.settings.limits.get();
console.log(limits.httpToolTimeoutMs); // 300000

await admin.settings.limits.put({
  limits: { httpToolTimeoutMs: 600_000, sessionQueuedMessages: 20 },
});

From a terminal:

npx nylorun tenant settings limits get
npx nylorun tenant settings limits put limits.json

How large, how many, and how long what crosses the Runtime may be is the Tenant's Runtime limits. They are a Tenant setting, set with a management key the same way on a local or a remote Tenant: admin.settings.limits, nylorun tenant settings limits, or GET / PUT /v1/tenant/limits. In Studio, the Tenant page's Limits tab lists them by area beside their defaults and edits one at a time.

Set limitsCopy Anchor Link

A put replaces them all. A limit left out takes its default. get returns every limit in force ({ limits }), with the default filled in for each the Tenant has not set, so putting back what get printed fixes today's defaults as the Tenant's own values. Keep the limits you change in one place, such as a limits.json in your repository holding only those, and put the whole set each time.

• A limit above its ceiling, or under its floor, is 400, naming the bound and why, and nothing changes.
• Each limit is read where it is checked, so a new value holds for the next request, write, call, or turn.
• An agent manifest's setup commands and input files are checked when it is saved, an Agent's labels whenever they are set, and a secret's value and hosts when it is written.
• An Agent made before a limit was lowered keeps running, within the lower limit where one applies at run time, such as a setup command's timeout or a disk version.

A name ending in Bytes counts bytes, Ms milliseconds, and Chars characters. Every value is a whole number, at least 1, except modelProviderRetries, triggerJitterPercent, and triggerJitterMaxMs, which may be 0.

What crossing one looks likeCopy Anchor Link

Elsewhere, the error message names the limit, its value, and where it is set (PUT /v1/tenant/limits).

Limits a harness getsCopy Anchor Link

A harness learns these in turn.start.limits and must respect them. A custom harness reads them there rather than assuming the defaults.

Limits only the Runtime checksCopy Anchor Link

The names that start with environment are kept from before Agents. They apply to an agent manifest's runtime section and to an Agent.

RequestsCopy Anchor Link

LabelsCopy Anchor Link

An agent manifest's runtime sectionCopy Anchor Link

Checked when the manifest is saved.

SecretsCopy Anchor Link

Checked when a secret is written, and a manifest's slots when it is saved.

Disk versionsCopy Anchor Link

Model callsCopy Anchor Link

See Timeouts and retries.

ToolsCopy Anchor Link

SessionsCopy Anchor Link

Triggers and wakesCopy Anchor Link

See Triggers and wakes.

MemoryCopy Anchor Link

See Agent memory. Checked on every write.

FlowsCopy Anchor Link

Agent manifestsCopy Anchor Link

What one agent manifest may hold, checked when it is saved.

npx nylorun check, npx nylorun apply, and packFolder() hold a folder to these defaults whatever the Tenant sets, so raising them helps only a client that uploads a folder itself, such as Studio's Upload folder….

CeilingsCopy Anchor Link

A ceiling is what the Runtime depends on, not configuration:

Lower limits for one agentCopy Anchor Link

An agent manifest's runtime section may set lower limits for the Agents made from it:

{
  "$schema": "https://docs.nylorun.com/schemas/agent-folder/v1/runtime.json",
  "kind": "pod",
  "limits": {
    "artifacts": { "fileBytes": 26214400 },
    "disk": { "versionEntries": 50000, "versionBytes": 2147483648 }
  }
}

In an agent manifest this is runtime.json; in a manifest document, its runtime section. A value above the Tenant's is refused when the manifest is saved, naming the limit. A limit left out is the Tenant's, as it is when the limit is checked. The Agent's limits (client.agents.get(id)) shows what is in force for it now. See Saving manifests.

Skill and artifact limitsCopy Anchor Link

Two other Tenant settings hold sizes, each a document with the same get and put:

await admin.settings.skills.put({ limits: { totalBytes: 4 * 1024 ** 3 } });

The Agents' compute settings, such as how many Agents a Tenant holds, are on Kubernetes.

Fixed valuesCopy Anchor Link

Some sizes stay fixed because a dependency or a standard fixes them: a 1 MiB record entry, the 64 MiB Harness API frame, and the longest JavaScript string and timer; a token's size, since a bearer token or a capability link arrives in a request's headers, and a page cursor's, which arrives in a URL; an artifact name's 255 characters and a folder path's 1,024; a link target's 4,096; W3C tracestate's 512 characters; a model-facing tool name's 64 characters, which every provider takes; and a Content-Type's 255. Identifier lengths are part of the protocol: an Agent's id and a subject 200, an agent manifest's name and a credential's name 64, a harness id 63, an application key's id and an issuer's name 32, an idempotency key 256.

ReferenceCopy Anchor Link

Next stepCopy Anchor Link