codex sessions aren't appearing on platform.openai.com/logs

What version of Codex is running?

main/e307040f1

Which model were you using?

gpt-5

What platform is your computer?

Darwin 25.0.0 arm64 arm

What steps can reproduce the bug?

Sometime after August 9th, all logs within https://platform.openai.com/logs for codex usage have seemingly vanished (if they were ever there before).

I noticed also, that reasoning content is no longer stored; instead an encrypted string (via b64) is persisted into the ~/.codex/sessions/.../session-name.jsonl file. I know that's for session continuation, however, Is that considered secret and not for public consumption? Is there any reason not to write out the full reasoning steps content, at least in RUST_LOG trace mode?

Sorry for asking directly, but @bolinfest / @seratch -- is this expected behavior?

I rather would have hoped there were traces of all codex interactions, to help debug issues, audit for users etc etc.... not sure how i feel that the 34M tokens i used in the past week aren't logged / traced in a discoverable way.

also: platform/logs is requesting a url like this:

URL: https://api.openai.com/v1/responses?created_after=1756011600&created_before=1756184399&include[]=message.input_image.image_url&include[]=web_search_call.action.sources&input_item_limit=1&model=gpt-5-2025-08-07&output_item_limit=1

However that's invalid:

{
  "error": {
    "message": "Invalid value: 'web...ces'. Supported values are: 'file_search_call.results', 'web_search_call.results', 'message.input_image.image_url', 'computer_call_output.output.image_url', 'reasoning.encrypted_content', and 'message.output_text.logprobs'.",
    "type": "invalid_request_error",
    "param": "include[1]",
    "code": "invalid_value"
  }
}

it's fixed if you remove web_search_call.action.sources. (@ReubenNarad you working on this?)

What is the expected behavior?

1. traces from codex sessions are discoverable on platform.openai.com/logs

1. understanding if reasoning is now protected content via encryption or not?

1. someone knows about the 400 on the api :)

What do you see instead?

_No response_

Additional information

_No response_