#Notifications

Step away from a running task and let Nourva tell you the moment it needs you or finishes the job.

#Overview

Notifications keep you connected to your work without keeping you watching it. When something needs your attention, or when a long job finishes, Nourva tells you — so you can leave a running task, do something else, and come back at exactly the right moment.

This matters most with the work that takes time: a deep investigation, a long Arachne run, a background job in the Shell. You should not have to sit and stare at a progress line. Notifications let you trust that Nourva will reach you when there is something worth reaching you for, and stay quiet when there is not.

#What you can do

  • Be told when a long-running job finishes, so you can start it and walk away.
  • Be told when a task needs you — when it pauses for your permission, hits a decision only you can make, or reaches a point where it needs your input to continue.
  • Step away from a running task with confidence that you will be called back when it matters.
  • Come back to the surface that needs you and pick up exactly where the work left off.
Note

A notification is one of the eight result formats too — an alert is a short, prominent notice surfaced right inside Nourva when something needs your attention. Notifications and alerts work hand in hand: the alert appears in your work, the notification reaches you when you have stepped away.

#How to use it

  1. Start a task that will take a while — a Deep Research investigation, an Arachne run, or a background job in the Shell.
  2. Choose a permission level that fits how much you want to be pulled back in. Lower levels (like Ask before acting) bring you a notification at each change; higher levels (like Act automatically) let the work flow and notify you mainly when it finishes or genuinely needs you.
  3. Leave the task running and go do other work. Nourva keeps going in the background and holds your place.
  4. When you are notified, return to the task. If it needs your input, give it; if it has finished, open the result.
  5. Tune how much you hear from Nourva in Settings — turning notifications on or off to match how present you want them to be.
Tip

Notifications and the permission levels are two halves of the same idea: the level decides how often a task pauses for you, and notifications make sure you know when it has. Pair a cautious level with notifications on when you are exploring; loosen the level for long, trusted jobs you only need to hear about at the end.

#Examples

text
Run a deep investigation on this topic and tell me when it's ready.

You start the investigation, close the window, and work on something else. When the report is finished, Nourva notifies you — you return and open a structured report with its sources gathered.

text
Build this site for me. I'll be away — let me know if you need anything.

Arachne works toward the goal on its own. The moment it reaches a step that needs your permission, you are notified, so you can approve it and let the work continue instead of finding it stalled later.

text
Kick off this long job in the Shell and ping me when it's done.

The job keeps running in the background. You step away, and Nourva tells you the moment it finishes — then you re-attach to the session and review exactly what happened.

#Tips

  • Use notifications as your signal to multitask: start the heavy work, get notified, and spend the wait on something else.
  • If a long task seems to have gone quiet, it may be paused for your approval at a stricter permission level — check the task; a notification should have reached you.
  • Turn notifications down when you are actively watching a task live, and back up when you plan to step away.
  • Remember that stopping always works immediately — being notified that a task needs you does not commit you to continuing it.