(Warning: This might accelerate capabilities.)
Idea inspired by o3 deep research API
Is there a way to put all outputs of previous o3 calls into a searchable database (MCP server) which can then be called by o3 again?
Search algo used can be embedding search or BM25 or a mix of both.
If you’re a large company you can aggregate many users outputs into one global public shared DB.
Searchable DB might be a better way to implement memory that the current approach of stuffing everything into the context window.
(It seems slightly nicer to be self-aware of when you’re posting capabilities ideas, but, insofar as it’s actually novel and useful, the damage is mostly done)
Hmm. You might be right. Maybe I shouldn’t have posted.
(Warning: This might accelerate capabilities.)
Idea inspired by o3 deep research API
Is there a way to put all outputs of previous o3 calls into a searchable database (MCP server) which can then be called by o3 again?
Search algo used can be embedding search or BM25 or a mix of both.
If you’re a large company you can aggregate many users outputs into one global public shared DB.
Searchable DB might be a better way to implement memory that the current approach of stuffing everything into the context window.
(It seems slightly nicer to be self-aware of when you’re posting capabilities ideas, but, insofar as it’s actually novel and useful, the damage is mostly done)
Hmm. You might be right. Maybe I shouldn’t have posted.