@delt/claude-alarm 1.2.0 → 1.4.0

package/README.md

@@ -77,7 +77,7 @@ Open `http://127.0.0.1:7900` in your browser.
 | `claude-alarm token` | Show auth token |
 | `claude-alarm test` | Send test notification |
 | `claude-alarm codex enable` / `disable` | Start (or stop starting) the Codex adapter with the hub |
-| `claude-alarm codex start` / `stop` / `status` | Run the Codex adapter on its own, e.g. when Codex runs on another PC. `start` tells you whether the adapter reached Codex and whether the hub answers at the configured address |
+| `claude-alarm codex start` / `stop` / `status` | Run the Codex adapter on its own, e.g. when Codex runs on another PC. `start` tells you whether the adapter reached Codex and whether the hub answers at the configured address; `stop` and `status` ask the running adapter itself |
 | `claude-alarm codex run --brief <file\|->` | Hand a task to Codex through the shared daemon and print the result as JSON (`--cwd`, `--thread`, `--name`, `--output-schema`, `--approval-timeout`, `--timeout`, `--yolo`; see `claude-alarm help`) |
 
 ## Tools Available to Claude
@@ -194,6 +194,7 @@ claude-alarm hub start
 - Questions Codex asks you (not approvals) still have to be answered in Codex; claude-alarm tells you one is waiting.
 - A conversation is followed only while Codex is working on it, so a closed Codex window drops off the dashboard about a minute later. If a reply could not be picked up, you get a **Reply not relayed** warning; read it in the Codex window. Conversations created from the dashboard are the exception (below).
 - If Codex runs on another PC, run `claude-alarm codex start` there. It reads the hub address and token from that PC's `~/.claude-alarm/config.json` (`hub.host`, `hub.port`, `hub.token`) or from `CLAUDE_ALARM_HUB_HOST`, `CLAUDE_ALARM_HUB_PORT` and `CLAUDE_ALARM_HUB_TOKEN`; the remote-hub answers you give `claude-alarm init` go only into that project's `.mcp.json` and do not apply here. `codex start` says whether it reached Codex and the hub. Keep claude-alarm at the same version on both PCs; an older hub cannot show Codex's choices.
+- Only one Codex adapter runs per user. A second one finds the first and stops (`codex start` says `already running`); an adapter the hub starts waits instead and takes over shortly after the other one stops. `claude-alarm codex stop` stops the adapter that is running now. If that was the hub's own adapter, the hub does not start it again until you restart the hub; to turn Codex off for good, use `codex disable` and restart the hub. claude-alarm 1.2.0 and earlier tracked the adapter in `~/.claude-alarm/codex.pid`; that file is no longer used, and `codex start` and `codex status` point it out if it names a running process.
 - **New Codex conversation from the dashboard**: click **+** in the session list. The Codex part appears only when a Codex adapter is connected to a running Codex daemon; claude-alarm does not start the daemon, so after a reboot open Codex once. Pick the PC if more than one is connected, type a folder on that PC or pick one of its recent Codex folders, and click **Create**. The new session is selected; send the first instruction from the message box.
 - Conversations created this way run with **full access and no approval prompts** (`danger-full-access`, approval policy `never`): Codex can run any command on that PC.
 - They stay on the dashboard until you close them with the session's **×** button (tap it, then tap **Close?** again). Closing only lets go of the conversation: it stays in Codex's history and can be continued in Codex. If Codex is still working, the task finishes first and the session drops off about a minute later. When the hub restarts, an adapter started by the hub restarts with it and these conversations drop off about a minute later.