RiskeyL 31cf2ff1ab fix: document both New Agent reply events in the streaming contract ...

The New Agent guide said replies stream as agent_message; the Send Chat Message SSE reference and the streaming guide said message. Verified against dify feat/agent-v2 (agent_app/app_runner.py and its unit tests): both fire — the reply streams incrementally as agent_message deltas, then the turn closes with a single message event carrying the complete answer, then message_end, with agent_thought alongside throughout. Document the full sequence on all three surfaces and tell clients to treat the closing message as the final answer rather than appending it. en/zh/ja; merged specs regenerated via the API pipeline (build + wire, coverage clean).

2026-07-09 18:17:29 +08:00

..

guides

fix: document both New Agent reply events in the streaming contract

2026-07-09 18:17:29 +08:00

openapi_chat.json

feat: consolidate and restructure the API reference (Phase 1) (#846)

2026-07-09 16:40:54 +08:00

openapi_chatflow.json

feat: consolidate and restructure the API reference (Phase 1) (#846)

2026-07-09 16:40:54 +08:00

openapi_completion.json

feat: consolidate and restructure the API reference (Phase 1) (#846)

2026-07-09 16:40:54 +08:00

openapi_knowledge.json

feat: consolidate and restructure the API reference (Phase 1) (#846)

2026-07-09 16:40:54 +08:00

openapi_service.json

fix: document both New Agent reply events in the streaming contract

2026-07-09 18:17:29 +08:00

openapi_workflow.json

feat: consolidate and restructure the API reference (Phase 1) (#846)

2026-07-09 16:40:54 +08:00