Skip to main content

Module request_keys

Module request_keys 

Source
Expand description

The key each model request carries, resolved when the request is sent (ModelRuntime.getAuth per request, so a /login, a changed auth.json or a refreshed OAuth token applies to the next request), and the request stack the session’s side lanes (frames, in-memory subagents, the predict adapter) send through.

  • Keys: --api-key is a runtime key of the provider it was given for (session-worker.ts setRuntimeApiKey(resolved.model.provider, apiKey)); every other provider resolves its own credentials. Ambient AWS or Google credentials (<authenticated>) authenticate a request without a key, so none is sent.
  • Keyed: a stream whose requests carry the key of their model’s provider unless the caller set one.
  • Retrying: the harness retry policy (settings.retry, read per request) over a stream, as a TypeScript harness lane retries a transient provider error.

Structs§

Keyed
A stream whose requests carry the key of their model’s provider, resolved per request, unless the caller set one.
Keys
Retrying
A stream that asks again after a transient provider error (isRetryableAssistantError), up to the policy’s retries with its backoff; an aborted request is never retried and the wait ends with the request’s signal.

Functions§

lane_stream
The stream a side lane of the session requests through as a TypeScript harness lane does: the live request settings and idle timeout (streamOptions, httpIdleTimeoutMs), the key of each request’s provider resolved per request, and the harness retry policy.
retry_policy
settings.retry of a settings manager (getRetrySettings): what the durable runtime retries a lane’s generation with.

Type Aliases§

ProviderCredentials
Resolves a provider’s own credentials (auth.json, models.json, the environment) now.
RetrySource
Reads the retry policy as the settings name it now.