Lewy Blue

> It's probably not advisable, then. I disagree, since it will overcome a common point of confusion and bring us in line with the standard used by [most other apps](https://github.com/mrdoob/three.js/issues/13373#issuecomment-408170437),...

Yes to this! Would ```THREE.App``` take some kind of configuration object? You'd at least need to be able to specify the camera and renderer type I guess. Also +1 for...

> What would an example look like when using render targets or other multiple scene, multiple camera situations? I was just giving this scenario some thought and agree that this...

For anyone else having this issue because pyenv-win is installed, see [the comment here](https://github.com/pyenv-win/pyenv-win/issues/469#issuecomment-1913364051): ``` export PYENV_ROOT="$HOME/.pyenv" export PATH="$PYENV_ROOT/bin:$PATH" # instead of `command -v pyenv >/dev/null || export PATH="$PYENV_ROOT/bin:$PATH"` eval...

It seems like system_prompt.txt in the project root is becoming an informal standard so maybe the extension can read that file?

> there could be a file per folder and not just in the root At that point, a RAG over the codebase would be the best solution. I'm not sure...