A2UI Launched: Full CopilotKit support at launch!

A2UI Launched: CopilotKit has partnered with Google to deliver full support in both CopilotKit and AG-UI!

Check it out
LogoLogo
  • Overview
  • Integrations
  • API Reference
  • Copilot Cloud
Slanted end borderSlanted end border
Slanted start borderSlanted start border
Select integration...

Please select an integration to view the sidebar content.

IntegrationsLanggraphCoagent troubleshooting

Migrate from v0.2 to v0.3

How to migrate from v0.2 to v0.3.

What's new in v0.3?

Starting with v0.3, we changed how messages are synced between the agent (LangGraph) and CopilotKit. Essentially, both will now share exactly the same message history.

This means that you need to return the messages you want to appear in CopilotKit chat from your LangGraph nodes, for example:

def my_node(state: State, config: RunnableConfig) -> State:
    response = # ... llm call ...
    return {
        "messages": response,
    }

All tool messages are now emitted by default, so you don't need to manually call copilotkit_customize_config to configure tool call emissions.

How do I migrate?

  1. Make sure to return any messages (tool calls or text messages) you want to be part of the message history from your LangGraph nodes.

  2. Optionally, remove manual copilotkit_customize_config calls when you want to emit tool calls.

  3. If you want to hide tool calls or messages from the chat, use copilotkit_customize_config and set emit_tool_calls or emit_messages to False. Make sure to not return these messages in your nodes so they don't become part of the message history.

PREV
Multi-Agent Flows
Slanted end borderSlanted end border
Slanted start borderSlanted start border
NEXT
Prebuilt Copilot UI

On this page

What's new in v0.3?
How do I migrate?