---
type: email
from: "chatgpt-codex-connector[bot]" <notifications@github.com>
subject: Re: [openai/openai-agents-python] Add Dapr session storage option (PR

 #1937)
received: 2026-03-06 08:08:54
date_header: Sun, 19 Oct 2025 09:59:54 -0700
priority: normal
status: awaiting_approval
uid: 33003
---

## Email Content

**From:** "chatgpt-codex-connector[bot]" <notifications@github.com>
**Subject:** Re: [openai/openai-agents-python] Add Dapr session storage option (PR

 #1937)
**Date:** Sun, 19 Oct 2025 09:59:54 -0700

### Body (preview)

@chatgpt-codex-connector[bot] commented on this pull request.





### 💡 Codex Review



Here are some automated review suggestions for this pull request.

    



<details> <summary>ℹ️ About Codex in GitHub</summary>

<br/>



Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

- Open a pull request for review

- Mark a draft as ready

- Comment "@codex review".



If Codex has suggestions, it will comment; otherwise it will react with 👍.









When you [sign up for Codex through ChatGPT](https://openai.com/codex), Codex can also answer questions or update the PR, like "@codex address that feedback".

            

</details>



> +    async def get_items(self, limit: int | None = None) -> list[TResponseInputItem]:

+        """Retrieve the conversation history for this session.

+

+        Args:

+            limit: Maximum number of items to retrieve. If None, retrieves all items.

+                   When specified, returns the latest N items in chronological order.

+

+        Returns:

+            List of input items representing the conversation history

+        """

+        async with self._lock:

+            # Get messages from state store

+            response = await self._dapr_client.get_state(

+                store_name=self._state_store_name,

+                key=self._messages_key,

+            )



**<sub><sub>![P1 Badge](https://img.shields.io/badge/P1-orange?style=flat)</sub></sub>  Honor strong consistency on read operations**



The `consistency` argument is stored but never applied when reading state. `get_items`, `add_items`’ initial fetch, `pop_item`, and `ping` all call `self._dapr_client.get_state(...)` without passing a `consistency` option, so even when a session is created with `consistency="strong"` the reads still use Dapr’s default eventual consistency. This makes the advertised strong consistency setting ineffective and can return stale history right after a write. P

---

## Suggested Actions
- [ ] Reply
- [ ] Archive
- [ ] Escalate
