I am not sure exactly what you are referring to here but if you are saying, “I don’t see the Code directory on my desktop”, it may be because you are using a DE that doesn’t show desktop files by default.
However, if you could provide more information as to what the issue is and where you are seeing it, that would allow us to provide better support.
Do you mean your bash prompt doesn’t show the current working directory?
In the Terminal Settings it has a Option to select, open as Login Shell. This way .bashrc sets the prompt Variable again.
By the way, pwd should print you the working directory any time.
Maybe you are using the Flatpak version of VS Code? In this case, due to the sandboxing, what you see, in particular the directory tree, inside the application could be different from what you see from the system point of view.
@alciregi yessir downloaded the .rpm & installed now working gracefully thanks.
everyone now solved thanks
Could you mark it as solved please?
Added flatpak
Please use the VSCode repo instead of downloading .rpm files.
Otherwise you wont get security updates, and VSCode is likely a pretty big target.
Also the obvious note that vscodium also has a Fedora repo and no tracking 
Just to add to your VSCodium recommendation: I like the idea and have used it for a long time but I recently switched back to Microsoft’s build for the Pylance plugin. While VS Code itself is open source, Pylance is not, the license explicitly states that you can only use it in the official build and the developers implemented a check that prevents it from running in other builds. You can remove that check in the plugin code after installing it, but I did not feel like a game of whac-a-mole with every plugin update.
Crazy, might want to file a bug for VSCodium? It may be easier for users to add a flag that changes the application name to “vscode” or something.
This can likely not be done in the app generally as it would be LeGaLlY FoRbIdDeN
I don’t think filing a bug would achieve anything, this is already known in the VSCodium GitHub project: the extension compatibility wiki page points out the closed source nature of Pylance, there is issue 1646 about Pylance not working (though I am not 100% sure if this is actually due to the check, IIRC Pylance points out the license incompatibility on startup, not just an error), and in a discussion thread people share the changes to the Pylance code to get it to work.
Also, I am not a JavaScript/TypeScript guy and the code is obfuscated beyond my abilities, I did not take a closer look at the actual check to see if it could even be circumvented by VSCodium. (Even if they did, this would probably turn into a cat and mouse game fast.) Frankly, the Jedi language server together with Pyright (which is the open source static type checking part of Pylance) is probably a better trade-off for someone who prefers VSCodium over the official VS Code build as they might frown at the closed source nature of Pylance as well.
An LSP 
Geez. . .