Skip to content
Effect 4.0 is here. One ecosystem. Zero dependencies.

AnthropicConfig unstable

The AnthropicConfig module lets a workflow temporarily customize the HTTP client used by generated Anthropic requests. It is used by AnthropicClient when request helpers run, so code can add middleware, logging, or other client changes without rebuilding the client layer.

3 exports Since v4.0.0 Source

Configuration

withClientTransform

unstable
Since v4.0.0

Runs an effect with an AnthropicConfig override that transforms the underlying HttpClient used by generated Anthropic requests.

When to use

Use when you need to apply a temporary HttpClient transformation, such as adding middleware or logging, to a specific scope of an effectful program.

Signature

declare const withClientTransform: {
  (transform: (client: HttpClient) => HttpClient): <A, E, R>(self: Effect<A, E, R>) => Effect<A, E, R>;
  <A, E, R>(self: Effect<A, E, R>, transform: (client: HttpClient) => HttpClient): Effect<A, E, R>;
}

Other

AnthropicConfig

unstable
Since v4.0.0

Namespace containing types associated with the AnthropicConfig service.

Services

AnthropicConfig

unstable
Since v4.0.0

Service tag for Anthropic client configuration overrides, such as transformations applied to the generated HTTP client.

When to use

Use when you need to provide or read Anthropic client configuration through Effect's context from a layer or integration.

See

Signature

declare class AnthropicConfig extends Shape<"@effect/ai-anthropic/AnthropicConfig", Service, this> {
  constructor(_: never);
  static readonly getOrUndefined: Effect<Service | undefined>;
}