R and radian paths per project folder/conda environment (i.e. make vscode-R design like vscode-python)

I'm new to VSCode (just moved from Atom because it's being retired), and I'm trying to understand how to set up the R extension to work seamlessly with conda environments at the project folder level. Each of the project folders in my workspace is associated with its own conda environment, with it's own R and radian builds/versions and libraries. But when I go to my settings, the R extension settings disappear when you look at the folder level vs workspace level.

How can I set up the R extension to automatically switch to the appropriate project folder conda environment R, radian, and libraries for the project file I currently have open within that specific project folder? VSCode can do this with python and I've set that up, so every time I open a code file from a specific project it just context switches to the appropriate conda environment, python, and libraries.

I want to do the same with R. But when I open an R file in a project folder, in the status bar it shows R: (not attached). When I try to attach it with an open terminal the auto-pasted .vsc.attach() doesn't work. Cannot figure out how to fix this.

Start by reviewing the R extension's folder- and workspace-level settings, the status-bar attachment flow, and the .vsc.attach() entry point described in the issue. Compare those behaviors with VS Code's project-level Python environment switching. Done would mean selecting the appropriate R, radian, and library environment for each project folder.