「UNBOUND x SHIFT UP」 Two powerhouses unite to develop a brand-new title. Stay tuned for the incredible synergy between Shinji Mikami's directorship and SHIFT UP! #MikamiShinji# #UNBOUND# #SHIFTUP#

My UNBOUND keynote is now officially in the books. Thought it went pretty well, but haven't watched the game tape yet. If you happened to see it either live or on livestream, would love your feedback. #unbound# #unbound26#

I'm at the HubSpot #UNBOUND# conference in Boston. With 13,000 of my closest friends. I love this community. Can already feel the positive vibes. Tonight: I'm holed up in my hotel room practicing my keynote for tomorrow. It's going to be a long night (like always) but I think you folks will like it.

# Practical and Useful Patterns for OpenAI Agent SDK 🌍 Unbounded history is the enemy of cost and latency! Use history control and compaction to keep context size optimal. 📌 Title: Sessions – Control history / Compaction 🔗 URL: 🧩 Overview Long-running sessions cause history bloat, driving up token costs and latency. Use `SessionSettings(limit=N)` to cap history to the most recent N items, `session_input_callback` for custom trimming and reordering, `OpenAIResponsesCompactionSession` for automatic compression, and manual `run_compaction()` for idle-time optimization. 🛠 Usage The simplest approach is `SessionSettings(limit=50)`. Create an agent with `Agent(name="assistant", instructions="Answer helpfully")` and a session with `SQLiteSession("user_12345")`, then pass the settings through `RunConfig`: `await "What's the latest?", session=session, run_config=RunConfig(session_settings=SessionSettings(limit=50)))`. Only the most recent 50 items are retrieved from the session. For advanced control, use `session_input_callback`. Define a `custom_history_filter(history, new_input)` function that keeps system messages via `h.role == "system"`, limits regular exchanges to `history[-20:]`, and returns `filtered + new_input` (`new_input` is a list). Pass it as `await "...", session=session, run_config=RunConfig(session_input_callback=custom_history_filter))`. For automatic compression, use `OpenAIResponsesCompactionSession`. Create `underlying = SQLiteSession("user_12345")`, wrap it with `OpenAIResponsesCompactionSession(session_id="user_12345", underlying_session=underlying)`, and run `await "Summarize our discussion so far", session=session)` — long conversations are automatically summarized and compacted. For manual compaction, disable auto-compaction with `OpenAIResponsesCompactionSession(session_id="user_12345", underlying_session=underlying, should_trigger_compaction=lambda _: False)` and call `await "force": True})`. Running this during user idle time improves latency on the next request. 🏗 Practical Patterns `SessionSettings(limit=50)` is the simplest cost control. Only the most recent 50 items are retrieved and sent to the model, while the default `limit=None` retrieves everything. This works well for customer support where recent exchanges matter most. `session_input_callback` is for advanced control. For example, always retain system messages and VIP customer flags while limiting regular exchanges to the most recent 20. The key insight is that it only filters what's sent to the LLM — storage remains unchanged. `OpenAIResponsesCompactionSession` performs automatic compression, summarizing long conversations into shorter representations to use the context window efficiently. For streaming-first applications, manually running `run_compaction()` during user idle time is effective. The next request starts from compacted history, improving time-to-first-token latency. 💡 Use Cases 💰 Token cost capping via limit settings 🔧 Selective context retention with custom callbacks 📦 Context optimization for long sessions via auto-compaction ⚡ Streaming-first latency improvement with idle-time compaction ⚠️ Caveats - `limit` caps how many items are retrieved, not what is stored — the session keeps the full history, but anything beyond the limit never reaches the model, so set the value carefully - `session_input_callback` runs on every request — avoid heavy processing - Auto-compaction depends on summarization accuracy; exact numbers and proper nouns may be lost - `run_compaction()` involves API calls, so calling it too frequently increases costs ✨ Proper history control keeps cost and latency optimal even in long-running sessions! #OpenAIAgentSDK# #AIAgent#

The day before I take the keynote stage at #UNBOUND# in Boston, my episode on the Marketing Against The Grain podcast dropped today. This was a fun conversation. We talk about the rise of the solopreneur (1 person companies) and YouSpot (the AI-native CRM for those solopreneurs). Let me know what you think or if you have any questions.

It is a profound honor to work alongside the top-tier creative team at Unbound. I am deeply moved to support the visionaries behind the legendary games I’ve cherished my whole life, especially a project directed by Shinji Mikami himself. We are currently preparing a diverse lineup—from massive blockbusters that will shock the world to experimental projects fueled by brilliant, sparkling ideas. Please look forward to what’s coming! #MikamiShinji# #UNBOUND# #SHIFTUP#