Keep chat history and retained memory from being confused.
Practical procedure
- For a direct chat-completions client, send the message history required for the current turn and remove unrelated or superseded context deliberately.
- Use workspace conversation records where the actual application provides them. Do not invent a previous_response_id field to link calls to an unsupported response API.
- Propose durable preferences through Memory Graph when retention is appropriate. Keep source evidence in Knowledge instead of treating every prior answer as a trusted fact.
Call the supported chat contract
Normal web chat and the customer CLI use GoCux Gateway. Provider routing stays inside the service. The model catalog advertises the GoCux route alias gocux-deep, not an upstream provider identity. A compatible chat client supplies its message history and an explicit data-classification header; GoCux applies identity, policy, paid admission and credit reservation before a provider request.
Contract example
Developer examples below describe routes on an authorized, configured GoCux control-plane base URL. They are request shapes or operation references, not claims that a particular public hostname exposes the API. Use the workspace for the corresponding human workflow; availability and permissions depend on the actual deployment.
POST /v1/chat/completions X-GoCux-Data-Classification: public Content-Type: application/json
{
"model": "gocux-deep",
"messages": [
{
"role": "user",
"content": "Summarize these supplied public notes."
}
],
"stream": false,
"max_completion_tokens": 512
}Inspect the result
Read the returned choices and handle an error response before showing a completed answer. When streaming, consume complete events and distinguish connection closure from a successful terminal result. GoCux route aliases are product contracts; do not let a client-selected upstream model bypass server routing or display provider identities as customer configuration.
What to keep explicit
Conversational continuity, saved history and approved memory have different scopes and lifecycles. A response identifier from another service cannot stand in for all three.
Handle incomplete and refused work
Declare X-GoCux-Data-Classification exactly once. A data_classification field in the chat-completions body is rejected rather than used as the declaration. Missing classification is unclassified and can be refused by policy. An optional Idempotency-Key helps identify an operation, but a paid replay can return 409 without replaying the original response or contacting the provider again.
Continue with related guides
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.