Process Conversation Followups

Changed on

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

Request

  • Base URL: https://api.omicos.cn (the document declares no server; this is the origin it was published from)
  • URL: https://api.omicos.cn/api/processes/{process_id}/conversations/{session_id}/followups
  • Auth: none declared

Path parameters

process_idstring required
session_idstring required

Headers

authorizationstring nullable
x-omicos-devicestring nullable
x-omicos-device-kindstring nullable
x-omicos-device-namestring nullable

Response

Successful Response

object required

Changes

  • ef3006b6f052Revision changes
    • info

      added the new optional header request parameter x-omicos-device

    • info

      added the new optional header request parameter x-omicos-device-kind

    • info

      added the new optional header request parameter x-omicos-device-name