revert: copilotkit 0.1.94 AG-UI upgrade (#754) — incompatible protocol#756
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #754. The AG-UI upgrade turned out to be a 4-layer protocol migration, not a dep bump, and I verified the event vocabularies are incompatible:
LangGraphAGUIAgentserves via.run()+EventEncoder, emitting AG-UI protocol events (RUN_STARTED / TEXT_MESSAGE_CONTENT / STEP_STARTED, LangGraph events buried inRAWenvelopes) as SSE.agentic_client.pyparses bare NDJSON lines, andagentic_worker.pyconsumes raw LangGraph event names (on_tool_start,on_tool_end,on_chat_model_end), which the frontend event parser also depends on.So the AG-UI stream doesn't match the client/worker/frontend contract — proven live on echo-next (run.failed / no assistant output). Restoring copilotkit 0.1.78 + LangGraphAgent (the format the pipeline was built for). The base64 GCP_SA_JSON fix (#755) is independent and stays.
The AG-UI migration is worth doing but as a scoped, tested project across all four layers (agent → client → worker → frontend), tracked in the backlog — not a reactive dep bump.
🤖 Generated with Claude Code