Would be nice to have built-in database backed per-project context tooling

What variant of Codex are you using?

0.106 CLI

What feature would you like to see?

I would love to see maybe some kind of tooling that codex can use to track what it does and describe the specs, changes, etc that it makes and then reference them instead of relying on searching through every file in the project over and over until it runs out of context then searches again because it forgot all the things it looked up.

Add a semantic search or something built-in to codex per directory or whatever where codex just writes down functions, descriptions, methods, definitions, classes, references, specs, dependencies, modules etc so the whole project is all nice and neatly organized and then codex can just search for semantic keywords and get the actual functions needed to perform the task, heck it could even use that instead of spamming the context window until it forgets everything and messes up everything trying to figure out what its doing..

I have recommended this before and it appears that this is still a much-needed critical piece that any code writing thing needs to have because otherwise how can it figure out what does what in a large project? Unless it happens to guess the exact right keyword, then doing a "search" isn't sufficient to finding where a function may be hiding - you need to be able to search by descriptions which are tied into functions, files, methods, references, dependencies, and modules.

I just saved your company millions of hours of compute time. Your welcome.

Additional information

_No response_