#Re-attaching to a session

Walk away, come back, and pick the live stream right back up — a running session is always there waiting for you to reconnect.

#Overview

A Shell session keeps running whether or not you are watching it. When you navigate to another surface, start a second task, or simply step away, the session and its work continue. Re-attaching is how you reconnect to a session that is still running and watch its live output again, exactly as if you had never left.

This matters because real work is rarely linear. You start a long build, switch to drafting a document, check on some research — and then you want to see how that build is doing. Re-attaching closes the loop: the session never depended on the window being open, so coming back to it is instant and lossless. You see what is happening now, and you can keep steering from where you stand.

#What you can do

Reconnect to a session that is still running and resume watching its live output, line by line, in real time.
Leave a session working and come back to it later — after switching surfaces, starting other tasks, or returning to Nourva entirely — without losing your place.
Pick up the full picture on return: the session's history is intact, so you see what already happened as well as what is happening now.
Keep steering once you are back: change the permission level, approve a held action, or stop the work — re-attaching gives you the same control you had before you left.
Return to a session whose command has already finished and review its durable receipt of everything that ran.

Note

Re-attaching is for a session that is still alive. If the command has already finished, the session's durable receipt holds the complete history and result, so you can review exactly what happened even though there is no longer a live stream to watch.

#How to use it

Start a session and let it run. A long job continues in the background whether or not you are watching it, so you are free to move on.
Go do other work — switch to another surface, start a second task, or step away from Nourva. The session keeps going on its own.
When you want to check in, return to the Shell and open the session you left. It is still there, holding its history and running state.
Re-attach to it. The live output reconnects and streams again from where it is now, and the earlier history is right above it so you have full context.
Carry on as before — watch the rest of the run, adjust the permission level, approve a held action, or stop the work. Everything you could do before you left, you can do now.

Tip

If you stepped away from a long job, turn on notifications so Nourva tells you when it finishes or when it needs you. Then you can re-attach at the right moment instead of checking repeatedly.

#Examples

What you ask

text

I started a build a while ago — let me see how it's going.

What you see

You return to the session and re-attach. The live output reconnects and the build's lines stream in again in real time, with the earlier steps still visible above so you can see the whole run at a glance.