Reset stuck Nomo session state — stop the watchdog, clear dead/phantom session rows and send the activity summary (heatmap and streak) now, without unpairing
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Nomo Reset?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/karrixlee-nomo-reset-72388b38)
---
name: nomo-reset
description: Reset stuck Nomo session state — stop the watchdog, clear dead/phantom session rows and send the activity summary (heatmap and streak) now, without unpairing
disable-model-invocation: true
---
Run this exact command in the terminal and show its output verbatim to the user:
```
NOMOR="__NOMO_ROOT__"; NOMOS="$HOME/.config/cc-status/hook-shim.sh"; [ -x "$NOMOR/scripts/run.sh" ] && exec "$NOMOR/scripts/run.sh" "$NOMOR/dist/reset.mjs"; [ -x "$NOMOS" ] && exec "$NOMOS" reset; echo "Nomo could not find its installed files - re-run: bunx nomo-ai --cursor"; exit 1
```
What it does (relay the printed summary):
- Stops the liveness watchdog if one is running (it verifies the pid really is the watchdog before
killing anything). The watchdog restarts automatically on the next session event.
- Sweeps the local session records: every record whose process is dead gets a best-effort "session
ended" signal sent to the phone so its row clears, then the record is deleted. Sessions whose
process is still alive are left untouched.
- Pairing and encryption keys are NOT touched — the phone stays paired. To disconnect entirely, use
`/nomo-unpair`.
One caveat specific to Cursor: a row is cleared here only when Nomo knows which Cursor process owns
it **and** that process has exited. A stale-looking row is therefore left alone in two cases — it
belongs to a Cursor that is still running, or Nomo could not identify its owning process at all (then
quitting Cursor does not clear it either). In both it is marked done after 30 quiet minutes and
retires on its own about an hour later.
It always exits 0 — "No watchdog running" / "No stale sessions to clear" are normal outcomes.