@jiangkoumo_: Pi officially published a tutorial on building a multi-user Agent on Cloudflare Durable Objects. A single Durable Object corresponds to one session, with state stored in the built-in SQLite. Multiple users can share the same link to join the same session and chat collaboratively…

Pi officially published a tutorial on building a multi-user Agent on Cloudflare Durable Objects. A single Durable Object corresponds to one session, with state stored in the built-in SQLite. Multiple users can share the same link to join the same session and chat collaboratively. The tutorial also demonstrates waking up after the page is closed to check the weather two minutes later. Session retrieval in the tutorial uses an isolated design. The main conversation dispatches the search-history task to a sub-agent, which only gets a plain-text substring search tool. It only searches user and assistant messages at the top level of the same session, and explicitly excludes its own messages as well as previously generated retrieval messages, preventing search results from becoming evidence for subsequent retrievals. Raw match records and intermediate tool calls from retrieval stay in the sub-conversation; the main conversation only receives a brief conclusion tagged with the conversation ID. The prompt explicitly requires a direct "not found" reply when nothing turns up. When a Durable Object is evicted or the retrieval tool is replayed, the code retrieves the original sub-conversation by task ID and continues execution. When creating a conversation, the receipt corresponding to the request ID is stored alongside the new conversation, so re-sending the same request after a disconnect won't create duplicates; concurrent inputs go into a persistent inbox queue and are queued. The due times of multiple tasks are projected onto a single underlying alarm. The official tutorial notes that the alarm may fire multiple times, so task-handling logic must remain idempotent — external calls cannot inherently guarantee exactly-once execution. This architecture is a useful reference for anyone building cross-conversation in-session retrieval or scheduled-task Agents. The official demo intentionally skips authentication; we only reviewed the official tutorial this time and did not deploy and run it locally.