#Running in the background

Start a long job, walk away, and let it run — Nourva tells you the moment it finishes.

#Overview

Some work takes time. A build, a long test run, a process that grinds through many steps — none of it needs you watching every line. In the Shell, a long-running job keeps going in the background while you do other work, somewhere else in Nourva or away from your machine entirely.

This matters because your attention is finite and the work is not. You do not have to babysit a running command, and you do not have to choose between starting a slow job and getting on with something else. You start the job, leave it running, and come back when it is done — or let Nourva come to you when it finishes.

#What you can do

  • Let a long-running command keep going in the background while you move on to other work.
  • Step away from a running job entirely and trust that it continues without you.
  • Be told when a background job finishes, so you do not have to keep checking.
  • Come back to a still-running session at any time and pick up where you left off.
  • Reconnect to a running session and watch its live output again, even after navigating away.
  • Review exactly what a session did through its durable receipt — nothing is lost if you close the window or your machine restarts.
  • Keep a session working in the background while you start or run other sessions alongside it.

#How to use it

  1. Start the job in a Shell session — type your request or command and let it run.
  2. When the work is long, leave it running and move on. The session keeps its history and its running state, so it continues in the background while you do other things, inside Nourva or away from it.
  3. Carry on with other work. You can switch to another surface, open another session, or step away from your machine entirely.
  4. Let Nourva tell you when it is done. You are notified when a long job finishes, so you can leave a running task and be told the moment it needs you or completes.
  5. Return when you are ready. Reopen the session to see its result, or re-attach while it is still running to watch the live output stream again.
  6. If you stepped far enough away that the window closed or your machine restarted, return to the session and read its durable receipt — the full history and result are still there, exactly as they happened.
Tip

Turn on notifications so you can fully step away from a running task. With them on, you do not have to keep checking back — Nourva tells you when the job finishes or when it needs you.

Note

Backgrounding does not change a session's permission level. If you left the session at a level that pauses for your approval, a step may be waiting for you when you return rather than fully finished. Re-attach to see whether the job is still running, done, or holding for permission.

#Examples

What you ask:

text
Run the full test suite and let me know when it's done — I'm going to keep working.

What you see: The Shell starts the run and the output begins streaming. You move on to other work. When the suite finishes, Nourva notifies you, and the session is waiting with the complete result and its durable receipt of everything that ran.

What you ask:

text
Build the project — this one takes a while.

What you see: The build starts and keeps running in the background while you do other things. You come back later, re-attach to the session, and the live output picks up right where it is — still streaming if the build is going, or showing the finished result if it has completed.

What you ask (after closing the window and reopening Nourva later):

text
What happened with the build I started earlier?

What you see: You return to the session and its durable receipt shows exactly what ran and how it ended — nothing was lost when the window closed.

#Tips

  • Match the permission level to how far you plan to step away. For a long job you trust and want to run unattended, a level that lets the work flow through means it can finish without waiting on you.
  • Keep notifications on for background work — that is what lets you leave the task entirely and be called back only when there is something to see.
  • Re-attaching is the fastest way to check on a still-running job: you reconnect to the live output instead of guessing from the outside.
  • You can have more than one session working at once. Background one long job and start another alongside it rather than waiting in line.
  • Stopping always works immediately, even on a backgrounded job. If you come back and want to halt the running command, stop it with kill; to end the whole session cleanly, use close.