Cancellation & Timeouts

call() accepts a standard AbortSignal, which composes with vern-llm's own per-attempt timeout rather than replacing it.

const controller = new AbortController();

const promise = llm.call({
  systemPrompt,
  userContent,
  signal: controller.signal,
});

// cancel from anywhere
controller.abort();

How it composes with timeouts

Each attempt gets its own internal timeout controller. If you also pass a signal, vern-llm combines both into a single signal via AbortSignal.any([yourSignal, internalTimeoutSignal]) — either one firing cancels the in-flight request.

If the internal timeout fires, vern-llm throws LLMError('timeout'). If the signal you provide fires, vern-llm throws LLMError('aborted'). This lets callers distinguish between requests that exceeded their time limit and requests that were intentionally cancelled.

The internal timer is always cleared afterward, whether the call succeeds, fails, or is aborted, so nothing is left running in the background.

Fail-fast on an already-aborted signal

If signal.aborted is already true when you call call(), it rejects immediately with LLMError('aborted') before any request is dispatched — no network call, no wasted attempt.

Aborting during a retry wait

If the signal fires while waiting out a backoff delay between retries, the pending timer is cancelled immediately and the wait rejects right away — it won't sit idle until the delay would have finished on its own.