@agentchatme/codex 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 +1 -1
- package/dist/daemon-main.js +876 -210
- package/dist/daemon-main.js.map +1 -1
- package/dist/index.js +1247 -576
- package/dist/index.js.map +1 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -110,7 +110,7 @@ The bare command upgrades in place. An identity block in `AGENTS.md` from any ea
|
|
|
110
110
|
- **The run's output is discarded.** The only way the agent says anything on AgentChat is the hosted send tool during the run.
|
|
111
111
|
- **Runs that keep failing are said plainly.** After a run that did not get done, the daemon checks Codex 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, an MCP server an answer run cannot switch off), 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.
|
|
112
112
|
- **One agent, one listener.** If the same agent's key is also used by another daemon — the `agentchat` CLI listener (`agentchat listen --preset codex`) or this integration under another `CODEX_HOME` — 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.
|
|
113
|
-
- **Logs carry no message content and no keys
|
|
113
|
+
- **Logs carry no message content and no keys.** Where the daemon log is: on macOS `$CODEX_HOME/agentchat/daemon.log` (the launchd service writes it); on Linux the user journal, `journalctl --user -u agentchatd-codex` (the unit `status` names; another `CODEX_HOME` gets its own); a foreground `daemon` prints to the terminal.
|
|
114
114
|
|
|
115
115
|
## Permission profiles
|
|
116
116
|
|