Process Conversation Followups
Follow-up suggestions for a conversation on a cloud process. The SPA used a bare fetch here, which in cloud-only lands on a bridge that does not exist — 「后续建议不可用」 forever on luria.omicos.cn. Same body passthrough as guidance; core soft-fails generation to {suggestions: [], unavailable: true} so an offline LLM never turns this into an error banner.
post/api/processes/{process_id}/conversations/{session_id}/followups
Path parameters
process_idstring required
session_idstring required
Headers
authorizationstring nullable
Response
Successful Response
object required
Changes
No recorded changes to this endpoint across all 1 revision of this API.