---------------------- Based on the information provided in the extracts, it seems like you might be encountering a known issue with Garden. In this GitHub issue (), a user reported a similar problem where the cloud project URL is not provided in the same REPL session after a successful

login

command. The issue occurs when a user logs in during a REPL session and then runs any command like

deploy

. The cloud URL is only provided if the user was already logged in before entering the REPL or if the user exits the REPL after login and re-enters it. The suggested solution in the issue is to restructure the cloud initialization and project creation part and go through it after login as well. However, this is a known bug and it's not clear from the extracts if it has been resolved yet. As a workaround, you could try logging in before starting the REPL session with

garden dev

, or exit and re-enter the REPL after logging in. If the issue persists, it might be helpful to check the Garden documentation () or their GitHub issues () for updates or further assistance. ----------------------

Note: you can ask me a follow up question by @ mentioning me again

:speech_balloon: ----------------------

---------------------- Based on the information provided in the extracts, it seems like you might be encountering a known issue with Garden. In this GitHub issue (), a user reported a similar problem where the connection often gets lost after a little while when running

garden exec <module-name> --interactive /bin/bash

, resulting in the freezing of the terminal. The expected behavior is the same as in local-mode (restoring in case of lost connection). However, the current workaround suggested is to kill the terminal and restart the command. Another GitHub issue () discusses a similar problem where port forwards get disconnected after a while when running the command for a while. The user had to restart the Garden process which can take a while, especially if code written since starting the process triggers image builds. These issues might be related to your problem. If the issue persists, it might be helpful to check the Garden documentation () or their GitHub issues () for updates or further assistance. ----------------------

Note: you can ask me a follow up question by @ mentioning me again

:speech_balloon: ----------------------

Same thing wiht Safari.

@microscopic-river-74022 I tried Safari and I'm seeing "Not connected to a CLI session. Please check that Garden is running in watch mode in your terminal and try again. Note that you must be on Garden Core version 0.12.42 or higher to use the command palette." I am on version 0.13.9

---------------------- Based on the information provided in the extracts, it seems like you might be encountering a known issue with Garden. In this GitHub issue (), a user reported a similar problem where the

exit

command from dev mode tries to connect with the cloud dashboard for a logged-out user. The expected behavior is that no connection should be made to the cloud once the user is logged out and the user should not see any warning related to the cloud. However, this is a known bug and it's not clear from the extracts if it has been resolved yet. As a workaround, you could try logging in before starting the REPL session with

garden dev

, or exit and re-enter the REPL after logging in. If the issue persists, it might be helpful to check the Garden documentation () or their GitHub issues () for updates or further assistance. ----------------------

Note: you can ask me a follow up question by @ mentioning me again

:speech_balloon: ----------------------