Member Junction
    Preparing search index...

    ZhipuLLM implementation is a sub-class of OpenAILLM that overrides the base URL to point to Z.AI's OpenAI-compatible API endpoint.

    Z.AI (Zhipu AI) develops the GLM (General Language Model) series including:

    • GLM 4.6, GLM 4.7, GLM 5

    The API is fully OpenAI-compatible, supporting chat completions, streaming, and structured outputs.

    Hierarchy (View Summary)

    Index

    Constructors

    Properties

    _additionalSettings: Record<string, any>

    Protected property to store additional provider-specific settings

    thinkingStreamState: ThinkingStreamState

    State tracking for streaming thinking extraction Providers should initialize this if they support thinking models

    Accessors

    • get AdditionalSettings(): Record<string, any>

      Get the current additional settings

      Returns Record<string, any>

    • get apiKey(): string

      Only sub-classes can access the API key

      Returns string

    • get OpenAI(): OpenAI

      Read only getter method to get the OpenAI instance

      Returns OpenAI

    • get SupportsPrefill(): boolean

      Whether this LLM provider supports assistant prefill (pre-seeding the start of the model's response). Providers that support prefill should override this to return true. This is used as a code-level default when database metadata (AIModelType/AIModel/AIModelVendor.SupportsPrefill) is null. Database values of true/false override this getter.

      Returns boolean

    • get SupportsStreaming(): boolean

      OpenAI supports streaming

      Returns boolean

    • get SupportsTools(): boolean

      OpenAI natively supports tool calling (tools / tool_calls / tool role messages).

      Subclasses targeting OpenAI-compatible gateways inherit this; one whose endpoint does NOT accept a tools array should override it back to false.

      Returns boolean

    Methods

    • Adds the native tool-calling fields to an outgoing request when the caller declared tools.

      OpenAI's tool_choice vocabulary is nearly the neutral one — 'auto' | 'none' | 'required' pass through unchanged; only the named form is reshaped. Parallelism is a top-level request field here, unlike Anthropic where it hangs off the choice object.

      Parameters

      • request: ChatCompletionCreateParams

        The request body being assembled (mutated in place)

      • params: ChatParams

        The chat params for this request

      Returns void

    • The result of a cancelled request, the same for every driver: a failed result with no choices, statusText 'cancelled', and an errorInfo that says Cancelled (Fatal, never failed over) — or, when the signal was aborted by a timeout, a retriable NetworkError.

      Parameters

      • startTime: Date
      • Optionaloptions: { error?: unknown; message?: string; signal?: AbortSignal }
        • Optionalerror?: unknown

          The error the abort raised, kept on exception.

        • Optionalmessage?: string

          The message to report; defaults to one naming the signal's reason.

        • Optionalsignal?: AbortSignal

          The request's abort signal, read for why it was aborted.

      Returns ChatResult

    • Per-request options handed to the OpenAI SDK as the SECOND argument of chat.completions.create(body, options) — distinct from the request BODY.

      The only option we set today is signal, which carries ChatParams.cancellationToken down to the SDK's fetch call so an abort (caller cancellation or an AIPromptRunner timeout) actually tears down the HTTP socket instead of merely abandoning the promise. This is honored on BOTH the streaming and non-streaming paths.

      The SDK's own retry loop checks options.signal.aborted before every attempt and throws APIUserAbortError rather than retrying, so a cancelled request stays cancelled.

      Returned as a structural literal (rather than the SDK's RequestOptions, which is not exported from the package root) — every field of RequestOptions is optional, so this is assignable to it.

      Parameters

      Returns { signal?: AbortSignal }

    • Process a chat completion request. If streaming is enabled and supported, this will route to the streaming implementation.

      Parameters

      Returns Promise<ChatResult>

    • Process multiple chat completion requests in parallel. This is useful for:

      • Generating multiple variations with different parameters (temperature, etc.)
      • Getting multiple responses to compare or select from
      • Improving reliability by sending the same request multiple times

      Parameters

      Returns Promise<ChatResult[]>

      Promise resolving to an array of ChatResults in the same order as the input params

    • Parameters

      Returns Promise<ClassifyResult>

      Classification through a driver method is deprecated along with the legacy AI Actions system, its only caller, and will be removed in the next major version. Most drivers do not implement it. Run an AI Prompt through AIPromptRunner (@memberjunction/ai-prompts) instead, which adds model selection, failover and cost tracking.

    • Clear all additional settings This is useful for resetting the state of the provider or when switching between different configurations.

      Returns void

    • Utility method to map a MemberJunction role to OpenAI role

      • system maps to system
      • user maps to user
      • assistant maps to assistant
      • anything else throws an error While the above is a direct 1:1 mapping, it is possible that OpenAI may have more roles in the future and this method will need to be updated for flexibility

      Parameters

      • role: string

      Returns "system" | "user" | "assistant"

    • Extract thinking content from non-streaming content This method handles case-insensitive extraction of thinking blocks

      Parameters

      • content: string

      Returns { content: string; thinking?: string }

    • Create the final response from streaming results for OpenAI

      Parameters

      • accumulatedContent: string
      • lastChunk: any
      • usage: any

      Returns ChatResult

    • Returns (and clears) any user-visible content the thinking-tag stripper is still holding back at the end of a stream. Mid-stream, processStreamChunkWithThinking holds back a trailing fragment that could be the start of a <think>/</think> tag so a split tag never leaks as partial text; once the stream ends, such a fragment is real content and must be emitted (bug A5).

      Only flushes when NOT inside a thinking block: an unterminated <think> block's buffered text is reasoning, not answer, and is left held back (never surfaced as visible content). Returns '' when thinking extraction isn't active (no state) or there's nothing to flush.

      Returns string

    • OpenAI supports image file inputs natively via vision.

      Values reflect OpenAI's documented chat-completions vision API hard limits (https://platform.openai.com/docs/guides/images-vision):

      • 512 MB total payload per request
      • 1500 individual image inputs per request
      • Supported formats: PNG, JPEG, WEBP, non-animated GIF

      Note: the docs specify NO per-image size cap — only the request-level payload ceiling. We therefore set MaxFileSize to the same 512 MB value so this layer never rejects a single file OpenAI would accept; the effective constraint is that the SUM of all files in a request stays under 512 MB, which callers must enforce.

      These are API-level constraints — consistent across vision-capable chat models (gpt-4o, gpt-4.1, gpt-4-turbo, etc.), not per-model — so returning them from the shared driver is correct. Subclasses/wrappers that target non-standard endpoints (Azure OpenAI with its 50 MB cap, OpenAI-compatible gateways, etc.) should override this method if their limits differ.

      Returns FileCapabilities

    • Extra request-body params merged into BOTH the streaming and non-streaming ChatCompletion requests, beyond the standard OpenAI schema. Default is none. Subclasses targeting OpenAI-compatible gateways override this to opt into provider extensions the OpenAI SDK passes through verbatim — e.g. OpenRouter returns usage.cost / usage.cost_details only when usage: { include: true } is sent on the request.

      Parameters

      Returns Record<string, unknown>

    • Get the thinking tag format for this provider Providers can override this to customize the thinking tag format

      Returns { close: string; open: string }

    • Template method for handling streaming chat completion This implements the common pattern across providers while delegating provider-specific logic to abstract methods.

      Parameters

      Returns Promise<ChatResult>

    • Initialize thinking stream state for streaming extraction

      Returns void

    • Whether a request ended because it was aborted: its signal is aborted, the error is an abort by name (AbortError, APIUserAbortError, RequestAbortedError), or IsProviderAbortError recognizes it.

      Parameters

      • error: unknown
      • Optionalsignal: AbortSignal

      Returns boolean

    • Recognizes an abort error the shared names miss. A driver whose SDK raises its own class for an aborted request overrides this. Default: false.

      Parameters

      • _error: unknown

      Returns boolean

    • Whether a message is framework-authored volatile state for this request only: the loop agent's trailing runtime-state fragment (date/time, scratchpad, payload, a relocated specialization), which is rebuilt every iteration and must never sit inside a provider's cached prefix.

      The base test is the VolatileStateMessageMetadata.volatileState flag the agent layer sets. A driver may override to recognise the message by other means (Anthropic also accepts the fragment's tag literal for callers that pass plain text), but should call super first.

      Parameters

      Returns boolean

    • Process streaming chunk with thinking extraction This method handles case-insensitive extraction across chunk boundaries

      Parameters

      • rawContent: string

      Returns string

    • Process a streaming chunk from OpenAI

      Parameters

      • chunk: any

      Returns { content: string; finishReason?: string; usage?: any }

    • Reset streaming state for a new request. Overrides the base-class hook so BaseLLM.handleStreamingChatCompletion calls this both at the start of a request AND in its finally block — releasing accumulated reasoning/ thinking buffers and preventing state from a prior request bleeding into the next. Inheriting providers (Cerebras, Fireworks, Groq, xAI, Zhipu, Inception, LlamaCpp, etc.) automatically benefit from this override. See audit R2-C5.

      Returns void

    • Reset thinking stream state

      Returns void

    • Set additional provider-specific settings Subclasses should override this method to validate required settings

      Parameters

      • settings: Record<string, any>

        Provider-specific settings

      Returns void

    • Splits an outgoing request around its trailing volatile-state message, so a driver can place its cache boundary on the last message of head and send tail uncached. Returns null when the request has no trailing volatile state, in which case the driver formats the whole list as usual. Neither array is a copy of the input's messages; only the list is new.

      Parameters

      Returns TrailingVolatileStateSplit

    • Parameters

      Returns Promise<SummarizeResult>

      Summarization through a driver method is deprecated along with the legacy AI Actions system, its only caller, and will be removed in the next major version. Run a summarization AI Prompt through AIPromptRunner (@memberjunction/ai-prompts) instead, which adds model selection, failover and cost tracking.

    • Check if the provider supports thinking models Providers should override this to return true if they support thinking extraction

      Returns boolean

    • Index of the trailing volatile-state message in an outgoing request, or -1 when there is none. The fragment is the LAST message, or the one before it when an assistant prefill has been appended after it. -1 is also returned when nothing precedes the fragment, because then there is no stable history for a provider to cache ahead of it.

      Parameters

      Returns number