Skip to main content
When Gateway I/O logs are on, Phaseo stores the prompt and response of each request. You can open any stored Chat Completions, Responses or Messages request in Chat, check how it rendered, and continue the conversation from there with the same model or a different one.

​
Before you start

  • Turn on Store request and response payloads in Settings → Privacy. Only requests made while it is on can be opened.
  • When Require zero data retention is on, the workspace never stores prompts or responses. Neither do requests made with an API key whose guardrail requires zero data retention, or requests that set require_zero_data_retention themselves. Their requests can’t be opened.
  • Requests sent to the regional endpoints (eu.api.phaseo.app and us.api.phaseo.app) aren’t stored, so they can’t be opened.
  • You need to be a member of the workspace the request belongs to. If Who can view contents is set to Owners and admins, only owners and admins can open its requests.

​
Open a request

Each turn of a session already contains the conversation up to that point, so opening a turn opens everything before it as well. The link Chat opens carries only the request ID, so you can share it with other members of the workspace. Chat loads the request again for whoever opens it, using their own access.

​
Choose what to carry over

Before the chat is created, Chat shows what the request contains and what will be kept. If the request’s model isn’t available in Chat, the chat uses your current model instead. You can change models after the chat opens.

​
How the chat continues

  • The request opens as a new chat with its own session ID, saved in your browser like any other chat. Continued turns don’t join the original session in Logs.
  • Messages you haven’t edited are sent in their original form, so tool calls, tool results, images, audio and files are kept on the next turn. Edited and new messages are sent as text, as in any chat.
  • You can switch models, compare several models side by side, branch or edit, as in any chat.
  • Continued turns run in your active workspace and are billed like any other Chat request.

​
What can’t be carried over

Chat lists anything it couldn’t carry over before you continue:
  • Turns kept by the provider through previous_response_id or a conversation ID. Only the turns in the request itself are stored.
  • Attachments sent by file ID or remote reference rather than inline.
  • Responses that failed, were cut short, or offered several choices (only the first is kept).
  • Tool calls that never received a result. These are sent as text.
  • Content types Chat can’t show, such as provider-specific blocks.
Requests too large to store, and requests whose stored content has expired or been deleted, can’t be opened. Only text requests can be opened in Chat. Image, audio, video and embeddings requests can’t.
Last modified on October 22, 2026