## [0.39.0] - 2026-09-09

> Requires spt-core **v0.66.0 or newer** (unchanged). Update with `spt adapter update claude-spt`. Plugin skeleton **0.1.19** — this release changes a skill, so reinstall the plugin as well.

### Changed
- **"Commune across" is now called "recharge".** The old name described the file the feature writes rather than what it does to you, and agents kept reading it as a way of signing off — the opposite of the truth, since your perch stays up the whole time and you come back with a fresh context window. The flag is now `/sptc:commune --recharge`. **Nothing you already know stops working:** `--across`, "commune across" and "commune to next session" are all still understood and will be for some time yet, so agents and notes carrying the old wording need no edit.

### Added
- **Your agent gets a nudge when it blocks waiting for a background task's output.** Running work in the background is what keeps an agent reachable while it works; sitting and waiting on that work's result gives the reachability straight back, and it is rarely necessary — finished background work wakes the agent on its own. The reminder is advisory and shares the same per-turn budget as the other reachability reminders, so a busy turn does not fill up with them.
- **A session started in a folder you have not opened before no longer hangs invisibly.** Claude Code asks for folder trust — and, for some project layouts, a second question about loading instructions from outside the folder — before it will start. With nobody watching a background session, it would sit at that prompt forever: spt reported the endpoint as started, and it simply never came online. Those approvals are now granted for the folder the session is about to open, in the same Claude Code account the session will actually use, so the session comes up instead of stalling. If it cannot be done, the launch says so and starts anyway rather than refusing.

### Fixed
- **Your session's colour comes back after a context reset, along with its name.** Claude Code drops both when a reset rotates the session; the name was already restored and the colour now rides along in the same step. Agents running under the alternate-account and ccs profiles get their own colours, so several sessions on one machine stay tellable apart at a glance.
- **Diagnostic history now survives long enough to diagnose something.** The adapter's hook log filled its size limit in under two hours — mostly with one repeated line — and, when it filled, was emptied outright by whichever agent happened to trip the limit, taking every other agent's history with it. The repeated line is now summarised, which stretches history to well over a day, and a full previous generation is kept instead of being discarded, so one agent's routine work can no longer destroy another's evidence.