langchain_core/langchain_community: add ControlMessage to langchain_core and enable passing messages with 'control' role through ChatOllama

[rylativity]

• Description: this creates a ControlMessage class in langchain_core for messages with the 'control' role, and allows passing messages with 'control' role through to ollama through ChatOllama. The update to langchain_ollama’s ChatOllama relies on the added ControlMessage class in langchain_core, so updates to both libs are included in this PR

• Issue: Granite 3.2 Thinking #30122

• Dependencies: no new dependencies

• PR title:

• PR message:

• Lint and test: format, lint, and test completed and passing in langchain_core and langchain_community.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
langchain	⬜️ Ignored (Inspect)	Visit Preview		Mar 9, 2025 3:41pm

[ccurme (ccurme)]

Several issues with this:

1. It's unlikely we are going to add a new message type to core until multiple large providers adopt something similar.
2. We should be updating langchain-ollama in libs/partners/ollama instead of the community implementation, which is deprecated (you should be seeing warning messages if you are using it).

Are you able to use use ChatMessage with a custom role for this instead?

[rylativity]

ccurme (@ccurme) a ChatMessage with a custom role can potentially work, but there is currently an incompatibility between the type of the role attribute in the ChatMessage class (which is a str) and the type of the role variable in ChatOllama's _convert_messages_to_ollama_messages method (which is a Literal)

Also, ChatOllama's _convert_messages_to_ollama_messages does not currently have an isinstance check for ChatMessages, so if you pass a ChatMessage to ChatOllama it raises an exception.

So in order to go that route, 1) the _convert_messages_to_ollama_messages method would need to be updated to handle ChatMessages like so:

...
 elif isinstance(message, ChatMessage):
    role = message.role
...

and 2) either the ChatMessage's role attribute would need to be changed to a literal (probably not ideal because that takes away its flexibility), or the "role" variable's type in _convert_messages_to_ollama_messages would need to be updated to accept the str type role attribute of a ChatMessage instance:

...
role: Literal["user", "assistant", "system", "tool", "control"] | str
...

The ChatMessage can technically work after addressing item 1) above, but the mypy typechecking will fail without implementing something like item2) above.

If you are ok with this proposed route ccurme (@ccurme) (open to any feedback or alternative suggestions), and if that would satisfy your requirements/use-case Clément PAPPALARDO (@lemassykoi), I am happy to make those changes and open a new PR.

[ccurme (ccurme)]

Very much appreciate the detailed plan! Let's go for it, we can work around / document the issues with role.

[rylativity]

New PR opened here - #30191 - much cleaner.

We can go ahead and close this in favor of #30191