When I launch the Forge console for the first time (or restart it), the initial context appears to be incorrectly set. Although the console shows that, Forge does not seem to recognize it.

As an example, the following console output shows different responses to the ls command without changing the current working directory:

[JDF]$ cd <TAB> 
hs_err_pid1248.log               jbdevstudio.ini                  
hs_err_pid1372.log               org.jboss.tools.vpe.browsersim/  
jbdevstudio                      
[JDF]$ pwd
/Users/vineet/workspaces/JDF
[JDF]$ cd <TAB>
.metadata/  RemoteSystemsTempFiles/  

This seems to affect path autocompletion mainly, but is also likely to affect Forge command execution that relies on the current working directory, since paths seem to be computed from JBDS root instead of the current workspace root for the very first time.