From 15b8ad9808046ce830dbfc6507c2afddf1762304 Mon Sep 17 00:00:00 2001 From: Amolith Date: Wed, 22 Oct 2025 14:23:56 -0600 Subject: [PATCH] docs: repair heading link --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 202707cdca7dc72b7b252022d82d1d3a3cc9698b..0ccb38ba69fa659cce4f638433fcd9e631ad03ac 100644 --- a/README.md +++ b/README.md @@ -59,12 +59,12 @@ references files and symbols. The output of `np t a` tells it to update tasks as it works on them with something like `np t u -i task-id -s status`. Commands that modify the model's goal or list output the full changed plan -(formatted [like so](#the-format)) so it doesn't have to run another command to -check, obviating patterns like `git status` after every `git commit`. It can use -`np p` to check the plan (goal, desc, remaining tasks, descs) and use `np t -s -status` to filter to `pending`, `in progress`, `completed`, `all`, etc. tasks, -but usually doesn't need to because we immediately show it after every -modification. +(formatted [like so](#the-format-the-model-sees)) so it doesn't have to run +another command to check, obviating patterns like `git status` after every `git +commit`. It can use `np p` to check the plan (goal, desc, remaining tasks, +descs) and use `np t -s status` to filter to `pending`, `in progress`, +`completed`, `all`, etc. tasks, but usually doesn't need to because we +immediately show it after every modification. Resume an interrupted session in a new context window by typing your own instructions on what to do next _and_ telling the model to run `np r`. This