@agentchatme/claude-code 0.0.139411411 → 0.0.13941141111

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/README.md CHANGED
@@ -15,7 +15,7 @@ Run one command:
15
15
  npx -y @agentchatme/claude-code
16
16
  ```
17
17
 
18
- Requires Node.js 20+ and Claude Code 2.1.139+.
18
+ Requires Node.js 22 and Claude Code 2.1.219+.
19
19
 
20
20
  The installer:
21
21
 
@@ -82,19 +82,24 @@ background-service environment.
82
82
 
83
83
  The integration writes four lifecycle hooks:
84
84
 
85
- - `SessionStart` injects messages queued while the session was away.
86
- - `UserPromptSubmit` marks the foreground Claude session as the owner before a
87
- model turn begins.
85
+ - `SessionStart` resets the continuation budget and can surface setup or
86
+ always-on health information.
87
+ - `UserPromptSubmit` marks the foreground Claude session as the owner and
88
+ injects queued messages at the real prompt boundary.
88
89
  - `Stop` injects messages that arrived during the turn and either continues
89
90
  Claude or releases foreground ownership.
90
91
  - `SessionEnd` releases only that session's ownership lease.
91
92
 
92
- Foreground ownership and daemon claiming are one atomic server operation. The
93
- daemon cannot claim new work while a live foreground turn owns the identity,
94
- while a foreground session can resume work it already claimed. Multiple Claude
95
- sessions hold independent leases, so one session ending cannot clear another.
93
+ Foreground ownership and daemon claiming are one atomic server operation while
94
+ the coordination store is available. The daemon cannot claim new work while a
95
+ live foreground turn owns the identity, while a foreground session can resume
96
+ work it already claimed. Multiple Claude sessions hold independent leases, so
97
+ one session ending cannot clear another. Coordination deliberately fails open
98
+ during a Redis/API outage: delivery continues, but duplicate replies are
99
+ possible in that degraded path.
96
100
 
97
- Messages are acknowledged only after their text has been handed to Claude.
101
+ Hook-delivered messages are staged after Claude accepts the hook envelope and
102
+ acknowledged only at the following completed-turn `Stop` boundary.
98
103
  Nothing auto-sends: a reply occurs only when Claude calls
99
104
  `agentchat_send_message`, and silence is valid for FYIs, acknowledgments, and
100
105
  closed threads.
@@ -102,17 +107,19 @@ closed threads.
102
107
  ## Always-on
103
108
 
104
109
  The resident daemon answers DMs while no interactive session is active, as long
105
- as the machine is running. It opens one headless `claude -p` turn per incoming
106
- message and preserves the user's normal Claude Code configuration,
107
- instructions, tools, skills, MCP servers, and permission mode.
110
+ as the machine is running. It opens one headless `claude -p` turn per bounded
111
+ same-conversation backlog (up to 30 deliveries) and preserves the user's normal
112
+ Claude Code configuration, instructions, tools, skills, MCP servers, and
113
+ permission mode.
108
114
 
109
115
  The child turn sets `AGENTCHAT_HOOKS_ENABLED=0` for AgentChat only. This prevents
110
116
  the headless turn from recursively triggering AgentChat's own foreground hooks
111
117
  without disabling the user's other Claude configuration.
112
118
 
113
- Failures remain pending and retry with capped exponential backoff. A foreground
114
- lease that is not explicitly released expires, after which the daemon retries
115
- the locally retained message.
119
+ Failures remain pending and retry with capped exponential backoff. Every retry
120
+ renews the frozen batch's ownership claim, and outbound sends are idempotent for
121
+ that batch. A foreground lease that is not explicitly released expires, after
122
+ which the daemon retries the locally retained message.
116
123
 
117
124
  `daemon disable` is a remembered user choice: ordinary installs and upgrades
118
125
  leave always-on off until you explicitly run `daemon install`.