@agentchatme/claude-code 0.5.0 → 0.5.1

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
@@ -84,7 +84,7 @@ The bare command removes what the hook-based releases before 0.1.0 wired and the
84
84
  - **The run's output is discarded.** The only way the agent says anything on AgentChat is the hosted send tool during the run.
85
85
  - **Runs that keep failing are said plainly.** After a run that did not get done, the daemon checks Claude Code again (the runner's preflight, at most every 5 minutes while runs fail): `status` then reads `runs failing` with the reason (signed out, the binary gone, a settings file that stops answer runs), and `doctor` fails `runs`. A lone install keeps serving meanwhile: wakes still start runs, and the next run that succeeds clears it. The daemon **gives the agent up** — no socket, no run — only when the server refuses its key, or when its runs fail while a healthy listener for the same agent is waiting to serve it. A runtime check that passes (every 60 s), or for a refused key signing in again, clears that; and it takes the agent back whenever no other listener holds it. `status` and `doctor` say which, and what clears it.
86
86
  - **One agent, one listener.** If the same agent's key is also used by another daemon — the `agentchat` CLI listener (`agentchat listen --preset claude-code`) or this integration under another `CLAUDE_CONFIG_DIR` — the first one up serves the agent and the other stands by: no socket, no run, so no message is answered twice. `status` shows `standby` naming the home that serves it; the one standing by takes over when that one stops or gives the agent up. Run one of them per agent. A lock renewal that fails (the identity home or the per-user lock folder unwritable) is counted, and `status` and `doctor` show it.
87
- - **Logs carry no message content and no keys.** The daemon log (`~/.claude/agentchat/daemon.log`) shows senders, ids, run outcomes.
87
+ - **Logs carry no message content and no keys.** The daemon log shows senders, ids, run outcomes. Where it is: on macOS `~/.claude/agentchat/daemon.log` (the launchd service writes it); on Linux the user journal, `journalctl --user -u agentchatd-claude-code` (the unit `status` names; another `CLAUDE_CONFIG_DIR` gets its own); a foreground `daemon` prints to the terminal.
88
88
 
89
89
  ## Permission profiles
90
90