claude-threads 1.40.1 → 1.41.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +22 -0
- package/dist/index.js +2688 -2476
- package/dist/mcp/mcp-server.js +55 -18
- package/docs/CONFIGURATION.md +2 -0
- package/package.json +4 -4
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,28 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [Unreleased]
|
|
9
|
+
|
|
10
|
+
## [1.41.0] - 2026-11-08
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
- **`lifecycleDelivery`: lifecycle notices without the notification** (#606). A new per-platform option next to `lifecycle` decides how a new status notice (idle warning, timeout, pause, shutdown, resume) reaches the thread: `post` (default, unchanged), `dedup` (when the bot's last post in the thread already shows the same notice, update that post in place instead of adding one, so back-to-back restarts leave one post instead of a stack) or `reaction` (an emoji on the bot's last post instead of a new post, which notifies nobody; a notice the bot had to post itself is updated in place instead). The deduped or reacted-to post is the one a 🔄 reaction resumes the session from. The abnormal-exit report (`[Exited: <code>]`) always posts, and `lifecycle: hidden` still delivers nothing.
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
- **`lifecycleDelivery` follow-ups** (#606). A notice is no longer refreshed above a newer post: every new reply in the thread now counts, including the bot's own permission prompts and command replies, which used to be missed. Under `reaction` the emoji no longer lands on a question, plan or prompt post, where it read as an answer option; the notice is posted instead. When swapping the emoji fails (idle warning to timed out, for example), the notice is posted and the stale emoji taken down, instead of leaving ⏳ on a session that already timed out.
|
|
17
|
+
- **Turns are attributed once a second person speaks in a thread.** Attribution used to count only invited users, so a thread where several platform-allowed users talked stayed unprefixed and Claude could not tell them apart. It now also counts the distinct people who actually spoke. Solo threads stay unprefixed (#640, #648).
|
|
18
|
+
|
|
19
|
+
### Changed
|
|
20
|
+
- `ws` 8.22.1, plus dev tooling (#662, #663).
|
|
21
|
+
|
|
22
|
+
## [1.40.2] - 2026-10-30
|
|
23
|
+
|
|
24
|
+
### Changed
|
|
25
|
+
- `hono` 4.13.14, plus dev tooling (#655, #656).
|
|
26
|
+
|
|
27
|
+
### Fixed
|
|
28
|
+
- **Auto-update respects `engines`.** The updater now skips a release this host's Node or Bun cannot run, logs why, and `!update` says so instead of reporting "Up to date". npm only warns about `engines`, so an update used to install anyway. A host that is held back gets no further releases until its runtime is upgraded (#659).
|
|
29
|
+
|
|
8
30
|
## [1.40.1] - 2026-10-30
|
|
9
31
|
|
|
10
32
|
### Added
|