Hi Akshay, the question in above for demo purpose. You can leave the process open even after you exit the terminal. Try **nohup q2 run &** , then you can close your terminal or vscode without disconnection, and the server log will be stored in nohup.out file under sdk folder. To restart or kill the process, re-visit terminal and use your stack name to find the process. **ps -ef | grep alex.jeong | grep "q2 run"** then take the process id and kill For instance **ps -ef | grep alex.jeong | grep "q2 run"** alex.jeong 11801 28635 1 16:14 pts/11 00:00:00 /home/alex.jeong@q2.com/sdk/.env/bin/python3.9 /home/alex.jeong@q2.com/sdk/.env/bin/q2 run Then **kill 11801**

Hi Akshay, the question in above for demo purpose. You can leave the process open even after you exit the terminal. Try **nohup q2 run &** , then you can close your terminal or vscode without disconnection, and the server log will be stored in nohup.out file under sdk folder. To restart or kill the process, re-visit terminal and use your stack name to find the process. **ps -ef | grep alex.jeong | grep "q2 run"** then take the process id and kill For instance **ps -ef | grep alex.jeong | grep "q2 run"** alex.jeong 11801 28635 1 16:14 pts/11 00:00:00 /home/alex.jeong@q2.com/sdk/.env/bin/python3.9 /home/alex.jeong@q2.com/sdk/.env/bin/q2 run Then **kill 11801**