View Source LangChain.Message.ContentPart (LangChain v0.3.3)

Models a ContentPart. Some LLMs support combining text, images, and possibly other content as part of a single user message or other content parts like "thinking" may be part of an assistant's response message. A ContentPart represents a block, or part, of a message's content that is all of one type.

Types

  • :text - The message part is text.
  • :image_url - The message part is a URL to an image.
  • :image - The message part is image data that is base64 encoded text.
  • :file - The message part is file data that is base64 encoded text.
  • :file_url - The message part is a URL to a file.
  • :thinking - A thinking block from a reasoning model like Anthropic.
  • :unsupported - A part that is not supported but may need to be present. This includes Anthropic's redacted_thinking block which has no value in being displayed because it is encrypted, but can be provided back to the LLM to maintain reasoning continuity. The specific parts of the data are stored in :options.

Fields

  • :content - Text content.
  • :options - Options that may be specific to the LLM for a particular message type. For example, multi-modal message (ones that include image data) use the :media option to specify the mimetype information. Options may also contain key-value settings like cache_control: true for models like Anthropic that support caching.

Image mime types

The :media option is used to specify the mime type of the image. Various LLMs handle this differently or perhaps not at all.

Examples:

  • media: :jpg - turns into "image/jpeg" or "image/jpg", depending on what the LLM accepts.
  • media: :png - turns into "image/png"
  • media: "image/webp" - stays as "image/webp". Any specified string value is passed through unchanged. This allows for future formats to be supported quickly.
  • When omitted, the LLM may error or some will accept it but may require the base64 encoded content data to be prefixed with the mime type information. Basically, you must handle the content needs yourself.

Summary

Functions

Create a new ContentPart that contains a file encoded as base64 data.

Create a new ContentPart that contains a URL to an file. Raises an exception if not valid.

Create a new ContentPart that contains an image encoded as base64 data. Raises an exception if not valid.

Create a new ContentPart that contains a URL to an image. Raises an exception if not valid.

Build a new message and return an :ok/:error tuple with the result.

Build a new message and return it or raise an error if invalid.

Create a new ContentPart that contains text. Raises an exception if not valid.

Types

@type t() :: %LangChain.Message.ContentPart{
  content: term(),
  options: term(),
  type: term()
}

Functions

Link to this function

file!(content, opts \\ [])

View Source
@spec file!(String.t(), Keyword.t()) :: t() | no_return()

Create a new ContentPart that contains a file encoded as base64 data.

Link to this function

file_url!(content, opts \\ [])

View Source
@spec file_url!(String.t(), Keyword.t()) :: t() | no_return()

Create a new ContentPart that contains a URL to an file. Raises an exception if not valid.

Link to this function

image!(content, opts \\ [])

View Source
@spec image!(String.t(), Keyword.t()) :: t() | no_return()

Create a new ContentPart that contains an image encoded as base64 data. Raises an exception if not valid.

Options

  • :media - Provide the "media type" for the image. Examples: "image/jpeg", "image/png", etc. ChatGPT does not require this but other LLMs may.
  • :detail - if the LLM supports it, most images must be resized or cropped before given to the LLM for analysis. A detail option may specify the level detail of the image to present to the LLM. The higher the detail, the more tokens consumed. Currently only supported by OpenAI and the values of "low", "high", and "auto".

ChatGPT requires media type information to prefix the base64 content. Setting the media: "image/jpeg" type will do that. Otherwise the data must be provided with the required prefix.

Anthropic requires the media type information to be submitted as separate information with the JSON request. This media option provides an abstraction to normalize the behavior.

Link to this function

image_url!(content, opts \\ [])

View Source
@spec image_url!(String.t(), Keyword.t()) :: t() | no_return()

Create a new ContentPart that contains a URL to an image. Raises an exception if not valid.

@spec new(attrs :: map()) :: {:ok, t()} | {:error, Ecto.Changeset.t()}

Build a new message and return an :ok/:error tuple with the result.

@spec new!(attrs :: map()) :: t() | no_return()

Build a new message and return it or raise an error if invalid.

Example

ContentPart.new!(%{type: :text, content: "Greetings!"})

ContentPart.new!(%{type: :image_url, content: "https://example.com/images/house.jpg"})
Link to this function

text!(content, opts \\ [])

View Source

Create a new ContentPart that contains text. Raises an exception if not valid.