Feature Request: Project-Scoped Context Injection for APIs

The project structure has given us a natural way to link cognitive context, but not a good way to leverage that outside of the natural browser or mobile chat interfaces.

Allow the response API and realtime-speech-to-speech API to accept a project parameter that automatically uses files and prior chats in that project as a part of the session context. Similar to a vector-store file search, this would be akin to a “project search”, enabling better re-use of existing chat threads and file collections which have already been cognitively linked by the user.

A feature like this reduces client engineering effort, improves token efficiency (by not having to re-establish context manually) and prevents duplication of file uploads for redundant vector store creation.

Enabling new conversational sessions to leverage prior knowledge more efficiently with less client engineering is an essential step forward.

Thank you.

Hey @tom21, totally get why you would want that. The idea of a project parameter for the Responses API and realtime speech-to-speech so sessions can automatically pull in that project’s files and prior chats makes a lot of sense, especially to cut down on re-sending context and duplicate uploads. Appreciate you taking the time to lay this out, your insights are genuinely helpful. I don’t have a timeline to share, but feedback like this is useful signal for where things could improve, and I’ll pass this along internally.

1 Like