# claude-mem v13.19.0

- Product: claude-mem (https://whatsnew.fyi/product/claude-mem)
- Vendor: claude-mem
- Date: 2026-08-31
- Version: v13.19.0
- Original notes: https://github.com/thedotmack/claude-mem/releases/tag/v13.19.0
- Permalink: https://whatsnew.fyi/product/claude-mem/releases/v13.19.0

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **added** — Add GET /restart endpoint that serves a page with a button to restart the memory worker
- **added** — Add POST restart functionality that waits until the replacement worker is up before reporting success
- **added** — Add npx claude-mem restart command as an alternative way to restart the memory worker
- **added** — Report pid in /health endpoint to verify worker restart
- **changed** — Move outage warning below injected context so it remains visible in long timeline output
- **changed** — Display outage warning in red in the terminal while keeping the agent's copy clean of ANSI escapes
- **security** — Protect restart page with POST requirement behind a real click instead of inert GET to prevent accidental restarts from image tags
- **security** — Add frame-ancestors CSP and X-Frame-Options DENY headers to prevent the restart page from being framed and harvested through overlay attacks

##### Restart the memory worker in one click

When the observer stops saving, the outage warning used to point at
`~/.claude-mem/settings.json`. A restart clears nearly every one of these
outages (a wedged or SIGKILL'd provider subprocess), so the warning now leads
with the restart, offered two ways:

```
Restarting the memory worker clears almost every outage. Do one of these:
  Click to restart:  http://localhost:37777/restart
  Or in a terminal:  npx claude-mem restart

Still failing after the restart? Run: npx claude-mem doctor
```

`GET /restart` serves a page whose button restarts the worker and waits until
the replacement is actually up before telling you so.

###### The warning is also easier to see

- **Moved below the injected context.** The timeline runs long enough that a
  warning at the top had already scrolled off by the time context finished
  printing.
- **Shown in red** in the terminal. The agent's copy stays clean — ANSI escapes
  there are just noise in the model's context.

###### Safety notes

The restart page is deliberately conservative:

- The `GET` is inert. Restarting is a `POST` behind a real click, so a page that
  merely names the URL in an `<img>` cannot bounce your worker.
- The route refuses to be framed (`frame-ancestors 'none'`, `X-Frame-Options:
  DENY`), so an attacker cannot frame it and harvest the click through an
  overlay.
- Success requires the successor, not the corpse: a *different* pid on `/health`
  (the dying worker answers for the whole graceful-shutdown window) **and**
  `/api/readiness` ok (a bound port is not a ready worker).

`/health` now reports `pid` to make that check possible.